Hiberden MCP Server

Read and verify your local media archive's 3-2-1 coverage across tape, disk, NAS, and cloud. Exposed over MCP by the hiberden mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Exposes the Hiberden archive engine (hiberden-core) as Model Context Protocol tools over the stdio transport (newline-delimited JSON-RPC 2.0).

Its toolset

Everything the assistant can do here goes through one of these:

• list_projects — none
• list_archives — project_id?, collection_id?, name?
• list_collections — project_id
• coverage_status — none
• archive_detail — archive_id
• list_destinations — none
• list_tapes — none
• tape_detail — serial
• recent_activity — limit?
• find_file — query, limit?
• list_archive_files — archive_id, offset?, limit?
• list_jobs — limit?

Configuration

You will need one environment variable: HIBERDEN_DB. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Hiberden's toolset — list_projects, list_archives, list_collections and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Agaveis; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Hiberden's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Hiberden.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the hiberden mcp server does with a few real requests.