Skip to content
stored
Sign inStart free

MCP-native

A URL and a key is the whole integration.

Connecting an agent is configuration, not code. Point any MCP-capable client at the remote MCP URL with your per-org API key, and it reads and writes shared memory immediately.

Start freeAll capabilities

Claude Desktop, Cursor, and Claude Code each connect to one remote MCP endpoint, wired to your shared memory.

Configuration, not code

Paste the config: that's the install

There is no SDK to add to your project and no MCP server to host. Drop the remote MCP URL and your per-org API key into your client's config, and the memory tools register on connect. The same endpoint and the same key work for every client; only the file it goes in differs.

  • Remote MCP URL + per-org API key — no SDK to install
  • Claude Desktop, Cursor, Claude Code — the same remote endpoint for each
  • Zero infrastructure — no Postgres, pgvector, or MCP server to run

remote MCP config

URL + key

Same endpoint, same per-org key. Pick your client:

{
  "mcpServers": {
    "stored": {
      "url": "https://mcp.stored.to/v1/sse",
      "headers": {
        "Authorization": "Bearer mm_live_your_org_key"
      }
    }
  }
}
https://mcp.stored.to/v1/sseno SDK · no server to run

Read and write on connect

Shared memory, immediately

Once connected, a client reads and writes the same shared memory the rest of your agents use. Memory tools register as soon as the connection is made, so an agent can start saving and retrieving against the shared graph right away, no extra setup step.

Keep exploring

Five capabilities, one shared memory.

Connect your first agent in minutes.

Start free