Obsideo MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| signup_start | Start Obsideo signup: emails a 6-digit verification code (12 GB free tier, no card, no expiry). 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_verify | Complete signup with the emailed code. Generates the Ed25519 account signing keypair locally (only the public half is sent), stores S3 credentials in ~/.obsideo/mcp.json. Re-running rotates credentials and keypair with no overlap; do not re-run to retry. |
| putA | Store a local file or inline content as an object. Optional encrypt=true encrypts client-side with AES-256-GCM using a locally generated, user-held key before upload (the platform then cannot read the object; key loss = data loss). Zero-byte objects are rejected. Objects are replicated to 3 providers and verified on a continuous cryptographic challenge cycle. |
| getA | Retrieve an object. Client-side-encrypted objects are decrypted automatically with the local key. Small text objects return inline; pass local_path for anything else. |
| ls | List stored objects (size TAB key), optionally under a prefix. |
| rm | Delete an object by key. |
| usageA | Show account storage usage versus quota. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Regan-Milne/obsideo-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server