Obsideo MCP

What Regan-Milne/obsideo-mcp MCP server does

Regan-Milne/obsideo-mcp MCP server connects an MCP-capable agent to Obsideo object storage. It supports ordinary object operations—uploading files or inline content, downloading them, listing keys, and deleting objects—as well as storage usage and plan information.

Uploads are encrypted with AES-256-GCM on the machine running the MCP server unless the encrypt: false option is selected. The encryption key is generated locally, and downloads are decrypted locally. Obsideo does not retain a copy of that key, so encrypted data depends on preserving the local credentials and key material.

The service is intended for application files, automated backups, agent artifacts, persistent memory, and other backup objects. It is not described as a CDN, queryable database, or sub-millisecond storage system.

How it works

The server normally communicates with an Obsideo coordinator and the storage providers named by that coordinator. Objects are replicated across three providers. The verify operation challenges providers with chunk-level Merkle proofs and checks their responses against a locally recorded Merkle root for objects uploaded by this server. It can therefore check possession without downloading the object again.

A proof result identifies providers that passed and reports providers that could not be challenged or failed. The coordinator supplies provider locations, challenge tokens, and the public keys used for signature checks. Objects uploaded through another system can be checked with a supplied local file; without that file, verification uses the coordinator's root and identifies that basis.

The server can create a no-email trial automatically when a storage operation is first used. The trial provides 100 MB for roughly seven days and uses proof-of-work. Email signup sends a six-digit code and provides a 12 GB free tier. If a trial is configured, completing signup claims that same account rather than creating a separate one.

Setup and configuration

Regan-Milne/obsideo-mcp MCP server can be installed in Claude Desktop by importing the released .mcpb extension. Other documented setups use Node's npx command:

{
  "mcpServers": {
    "obsideo": {
      "command": "npx",
      "args": ["-y", "obsideo-mcp"]
    }
  }
}

Claude Code uses claude mcp add obsideo -- npx -y obsideo-mcp; Cursor and Cline use the same command in their MCP settings. The documented Hermes Agent setup requires Node 18 or newer and adds the server with hermes mcp add obsideo --command npx --args -y obsideo-mcp.

Credentials, the signing key, and the encryption key are stored under ~/.obsideo/. Run backup_keys after account creation with either a .tar.gz destination or a directory. The backup includes credentials, keys, and upload commitments. There is no default destination, and Obsideo cannot recover a lost encryption key.

Tools and capabilities

• trial, signup_start, and signup_verify create or upgrade an account.
• put, get, ls, and rm manage stored objects.
• verify checks provider-held data without downloading the object.
• usage reports consumed and available storage and the current plan.
• backup_keys exports local credentials, keys, and upload commitments.
• plan reports free or paid status, billing period details, and pending offers.
• upgrade returns a Stripe checkout link for 200 GB blocks; it does not charge or resize a plan itself.
• portal returns a Stripe billing portal link for cancellation, payment-method changes, and invoices.

Limitations and notes

Regan-Milne/obsideo-mcp MCP server requires careful handling of ~/.obsideo/mcp.json and related local state. Losing the encryption key makes encrypted objects permanently unreadable. Losing roots.json does not remove the data, but it weakens local proof verification for affected uploads.

Encrypted objects are not described as shareable between people or machines. Select encrypt: false only when another tool needs to read the stored bytes directly, such as through S3-compatible access. The legacy S3 gateway remains available for older configurations or when OBSIDEO_TRANSPORT=s3 is set; stored objects remain compatible between transport modes.

Paid storage uses 200 GB blocks through Stripe. The upgrade tool only produces a checkout link, and changing or cancelling billing requires human action. Cancellation keeps stored data readable until the paid period ends, after which the account returns to its free quota.