The MCP connector

Ask your archive
anything.

Hiberden speaks the Model Context Protocol, the open language AI assistants use. Connect Claude Desktop, Cursor, or Windsurf to your catalog and ask in plain words.

  • Claude
  • Gemini
  • and other assistants that run MCP servers on your computer

hiberden mcp connected·read-only

❯make me a client-ready manifest for the Meridian delivery: every file, size, and checksum

hiberden·list_archive_files

Meridian_Delivery·2,341 files·4.8 TB·verified

All three copies are verified, so every checksum below is proven against the stored data, not just recorded. Here's the manifest:

MER_0417_conform.mov212.4 GBsha256 9f3c…41aa

MER_0417_audio_stems.zip48.1 GBsha256 c07d…8be2

MER_delivery_notes.pdf2.1 MBsha256 5512…97f0

… 2,338 more files

I can format this as a PDF with a cover page, or a CSV for their intake system. Which would you like?

❯

Sample data. The export feature you were about to request is now a sentence.
  • Built into Hiberden
  • No extra install
  • Read-only by default

If the catalog knows it, you can ask it.

Hiberden's catalog already tracks every project, archive, copy, tape, and file fingerprint it has ever written. The connector turns all of that into answers: plain language in, real answers out. No query language, no export menu, no waiting on a feature request.

  • Which archives are missing a copy their policy calls for?

    Coverage is checked against your own policy, archive by archive, and the gaps are named.

  • What's on tape HIB-0042?

    Answered from the catalog while the cartridge stays on the shelf: every archive that begins on it. No drive, no mounting.

  • Find every version of final_mix.wav.

    Searched by file name in the catalog, with each file's size, its archive, and the copies that hold it.

  • Which archives in the Aurora project have a verified tape copy?

    Each archive's copies and their status, answered from the catalog before you walk to the shelf.

  • Read the NAS copy of the March masters back and verify it.

    A real verification runs on your machine and reports what it found: Verified, Failed, or Missing, naming the check that ran.

  • What did we archive last month, and how big was it?

    Recent activity, summarized however you want it sliced.

  • Build a CSV of every archive, its size, and its last verified date.

    Reports built straight from the catalog: manifests, coverage audits, capacity roll-ups, insurance renewals.

  • Did last night's archive run finish?

    Job history is part of the catalog too: what ran, what failed, and why.

  • Set up a Season 3 project and file these six archives into it. Archive access

    Catalog housekeeping, done conversationally, once you raise the level.

  • Create a policy with the NAS, the cloud bucket, and tape, and assign it to Raw Footage. Full access

    Protection changes live at the highest level, and only if you granted it.

Projects, archives, copies, files, and jobs: each one is a question away.

What happened overnight? Just ask.

Long jobs finish while you are doing something else, and the questions come later. The connector reads Hiberden's job history the way it reads everything else, so your assistant can tell you what ran, what finished, what failed and why, and what happens next. The answer that used to mean digging through logs is now the first thing it says.

hiberden mcp connected·read-only

❯did last night's archive run finish?

hiberden·list_jobs

3 jobs·2 completed·1 failed

The tape and NAS copies of Night_Renders_0715 finished and verified. The cloud upload failed at 02:14, 41 GB in: the transfer session expired mid-upload.

You still have two verified copies in the meantime. Re-run the upload in Hiberden and ask me again: I'll confirm when all three copies are verified.

❯

Sample data. Job history is read-only; the one default-level tool that writes anything is a verification, which records its own result.

You grant a level, not a blank check.

The connector's permissions are a setting inside Hiberden, on your machine, set by you. An assistant can never raise its own access. Tools above its level are never offered to it, and if it calls one by name anyway, Hiberden refuses the call and records the attempt.

  1. 01 · Read-only

    Look, verify, report.

    The default. Search, coverage, job history, verification, and every report on this page. Nothing about your setup changes: no projects, no destinations, no policies. The only thing its tools write is the outcome of a verification you asked for, which is the point of running one.

  2. 02 · Archive

    Organize the catalog.

    Adds housekeeping: create projects and Collections, rename, and re-file archives. The archived data itself is never touched.

  3. 03 · Full

    Shape the protection.

    Adds destinations and policies: the decisions about where copies live. A cloud destination and its keys are set up in Hiberden itself, never through the connector.

The delete switch

Deleting anything needs the Full level and its own separate switch, which is off by default. Even switched on, Hiberden itself refuses removals that would silently orphan your data.

The Hiberden Settings window on its MCP tab: three access levels with Archive selected, the delete override toggle off, and an audit trail listing assistant actions, including two denied attempts.
Real screen from the app, sample data. The whole permission model is one Settings tab.

Every change an assistant makes lands in an audit trail you can read in the app: what was done, when, and which calls your permission settings refused. Completed verifications are written there too, naming the check that ran. Trust, with receipts.

It answers with catalog facts, not your files.

The catalog is a local database on your computer, and the connector is a local process beside it. There is no Hiberden cloud in this loop: the connector sends nothing about your archive to us.

Answers come from catalog records: names, sizes, dates, locations, checksums, history. The archived files themselves are never handed to the assistant. When you ask for a verification of a disk or NAS copy, Hiberden reads the copy on your side and reports the verdict, not the data. You can ask for the full check, which re-reads against SHA-256, the recorded BLAKE3, and the archive's signature when it has one, or the quick one, which re-reads against BLAKE3 for speed. Only the full check can mark a copy Verified, and the answer always says which one ran.

Your assistant may send your question, and what the connector returns to it, to its own provider to write the answer; that part is your AI client's, under its terms. Your cloud keys never take that path: they are entered in Hiberden and stay there, and neither the connector nor the assistant ever sees them.

The audit trail in Hiberden's MCP settings: a delete attempt denied because the override is off, a policy creation denied for needing the Full level, and two catalog changes recorded as ok.
Append-only receipts: every change an assistant makes, and every call your settings refused, recorded on your machine.

Read the connector's full privacy policy

Connected in a minute.

  1. 01Open Settings, then MCP, in the Hiberden app and pick the access level.
  2. 02In the Connect your AI assistant card, press Connect Claude Desktop. Hiberden writes itself into Claude Desktop, Cursor, or Windsurf if it finds them, leaving their other connectors alone. For another assistant that runs MCP servers on your computer, press Copy config and add the server entry it copies to that assistant's MCP settings.
  3. 03Ask your first question.

MCP is an open standard, and that's the point: the same connector works with any assistant that runs MCP servers on your computer. There is no Hiberden plugin to wait for, here or anywhere.

Give your archive a voice.

Try the whole thing free for 30 days, connector included, every feature on. The built-in virtual tape drive means you can archive, verify, and interrogate a full 3-2-1 setup before you own a single cartridge.

Free Trial

Windows 10+, Linux, and macOS · Free 30-day trial · Connector included