Skip to main content
Glama
Obsideo MCP server

Obsideo MCP server

by Regan-Milne

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OBSIDEO_TRANSPORTNoSet to 's3' to use the S3 gateway transport with the SigV4 keypair instead of the default direct coordinator transport.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
trialA

Create a free Obsideo account with no email and no human in the loop: a small proof-of-work and a ~10 second wait in place of identity. Returns a real account on the production network (100 MB, about 7 days, RF=3 replication, continuous possession proofs) and saves credentials locally. You usually do NOT need to call this: the first put/get/ls/usage auto-creates a trial if no account is configured. Call it to provision explicitly. To keep data beyond the trial, claim it with an email via signup_start (same account and data, quota rises to 8 GB free with no card and no expiry; 16 GB after the account holder answers eight questions in the Drive web app). Takes about 15 to 30 seconds (proof of work plus a 10 second issuance window); progress is reported while it runs.

signup_startA

Start Obsideo signup: emails a 6-digit verification code (8 GB free, no card, no expiry; 16 GB after the account holder answers eight questions in the Drive web app). If a no-email trial is configured on this machine, this CLAIMS it in place: same account, bucket, keys and data, only the quota rises. Otherwise it creates a new account for the email. Use a real inbox you or your human can read; documentation placeholders and disposable domains are refused with labeled errors. Then call signup_verify.

signup_verifyA

Complete signup with the emailed code. When claiming a trial, nothing but the quota and the identity changes (credentials stay valid, no propagation wait). For a new account, generates the Ed25519 account signing keypair locally (only the public half is sent) and stores S3 credentials in ~/.obsideo/mcp.json; re-running that path rotates credentials and keypair with no overlap, so do not re-run to retry.

putA

Store a local file or inline content as an object. ENCRYPTED BY DEFAULT: the bytes are encrypted client-side with AES-256-GCM using a locally generated, user-held key before they leave the machine, so the platform stores ciphertext it cannot read. The key lives only in the local config file and Obsideo has no copy: if the user loses it the data is unrecoverable, so tell them to back it up. Pass encrypt=false only when another tool must read the stored bytes directly (S3 interop); that stores plaintext. Zero-byte objects are rejected. Objects are replicated to 3 providers and verified on a continuous cryptographic challenge cycle. The first call on a fresh machine also creates the account and can take 20 to 50 seconds; progress is reported while it runs. Encrypted objects are readable only with this machine's key: there is no cross-user sharing of encrypted objects.

getA

Retrieve an object. Encrypted objects (the default for anything stored through this server) are decrypted automatically with the local key; retrieval from a machine without that key will fail, which is the intended property. Small text objects return inline; pass local_path for anything else. WRITES TO DISK: passing local_path writes the bytes to that path and overwrites any existing file there, so treat it as a write operation and confirm the path with your human first.

lsB

List stored objects (size TAB key), optionally under a prefix.

rmC

Delete an object by key.

verifyA

Independently verify that the network still holds an object, without downloading it. Challenges each provider directly and compares every answer, on this machine, against a merkle root. For objects stored through this server, that root is the one this machine recorded at upload time, if the local record still has it. Pass local_path (your copy of the stored file) to compare against a root computed from that file instead. If neither is available, it falls back to the coordinator's recorded root and says so. The coordinator chooses which providers to ask, where to reach them, and the public keys their signatures are checked against, and issues the challenge tokens. Each provider is challenged on one randomly chosen chunk. Returns how many providers proved possession right now, how many of those answers were signed, and whether any returned bad data.

usageA

Show account storage usage versus quota.

planA

Show the account's plan: free tier or paid blocks (200 GB per block, $5/month each), status, period end, and any upgrade offer waiting for the human's agreement. Never changes anything and never contacts Stripe.

upgradeA

Get a Stripe-hosted checkout link for a paid plan of N x 200 GB blocks at $5/month per block. This tool charges NOTHING and changes nothing: the human opens the link and pays on Stripe's page, and the quota rises after payment. Call it only when the human has asked for more space, and hand the link back to them; do not open or submit it yourself. If the account already has a paid plan this returns the plan instead (plan size is never changed from here; only the human's click on Obsideo's emailed agree link does that).

portalA

Get the Stripe Customer Portal link for a paid plan: cancel, change card, download invoices. For the human to open. Cancelling keeps everything stored and readable; the account returns to its free quota at the end of the paid period.

backup_keysA

Copy everything needed to recover this account's data (credentials, account signing key, encryption key, upload commitments) to a destination: one you are already authorized to use for backups, or one your human names. Obsideo holds no copy of the encryption key: if the local file is lost, encrypted objects are unrecoverable no matter how many providers hold them. Until this has been run, the only copy is on this machine, so it is worth running once after the account is created and again after any signup that rotates keys. A .tar.gz path produces one archive; a directory path produces plain copies. With no destination it refuses rather than choosing one.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 13 tools

Disambiguation4/5

Core object operations (put/get/ls/rm) and verification/backup tools are clearly distinct, and account lifecycle tools separate cleanly along trial vs email signup vs code verification. The only soft overlaps are portal vs upgrade (both mint Stripe links) and plan vs usage (both report account state), and the descriptions do enough to disambiguate them.

Naming Consistency3/5

The set mixes terse Unix-style verbs (put, get, ls, rm) with noun-first compounds (signup_start, signup_verify) and noun-only names (plan, portal, usage, trial). Also inconsistent within the same family: signup_start puts the verb second while backup_keys puts it first, so there is no single predictable pattern.

Tool Count5/5

13 tools is well inside the sensible range and each one maps to a distinct need: object CRUD, integrity verification, key backup, trial/email signup, usage/plan visibility, and billing links. Nothing looks like a redundant wrapper or an orphan tool.

Completeness4/5

Object lifecycle (store, list, retrieve, delete), integrity verification, disaster-recovery backup, and account/quota/billing flows are all covered, so agents won't hit dead ends on core workflows. Gaps are minor: no metadata/stat or copy/move operation, no account deletion or credential-rotation tool exposed outside re-running signup, and no batch operations.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues