TUNC.AIORB

TUNC.AI / Tunc Orb guides

Give Claude Code, Cursor and ChatGPT the same memory

Connect every AI app you use to one Tunc Orb, so what one agent saves, the others can read, on any computer.

Updated

Each AI app keeps its own memory: what you tell Claude Code stays in Claude Code, and Cursor or ChatGPT start from nothing. Tunc Orb is one private store for all of them. Connect each app to the same MCP server and they read and save the same named records and logs.

1. Connect each app

Every client signs in with your Tunc account in the browser; nothing to install. If you have no Tunc account yet, you create one, free, during that first sign-in. The server URL is https://mcp.tuncorb.com/mcp.

ClientSteps
claude.ai, Claude Desktop and Claude mobileSettings → Connectors → Add custom connector → name Tunc Orb, URL https://mcp.tuncorb.com/mcp → Add → Connect.
Claude CodeAdd the server, then run /mcp, choose tunc-orb and Authenticate.
claude mcp add --transport http tunc-orb https://mcp.tuncorb.com/mcp
ChatGPTSettings → Apps & Connectors → Advanced → turn on Developer mode → Create → name Tunc Orb, URL https://mcp.tuncorb.com/mcp, Authentication OAuth → Create → Connect.
CursorAdd it to ~/.cursor/mcp.json, then Settings → MCP: it shows “Needs login” → Login.
{
  "mcpServers": {
    "tunc-orb": {
      "url": "https://mcp.tuncorb.com/mcp"
    }
  }
}
VS Code (Copilot)Command Palette → MCP: Add Server → HTTP → https://mcp.tuncorb.com/mcp → name tunc-orb → allow the sign-in prompt.
Gemini CLIAdd it to settings.json, then run /mcp auth tunc-orb.
{
  "mcpServers": {
    "tunc-orb": {
      "httpUrl": "https://mcp.tuncorb.com/mcp"
    }
  }
}
Copilot StudioTools → Add a tool → New tool → Model Context Protocol → URL https://mcp.tuncorb.com/mcp → Authentication OAuth 2.0, Dynamic discovery.

2. Save in one app, read in another

Ask one agent to save something by name, then ask another to read it. In Claude Code: "Save our decisions about the billing refactor to Tunc Orb as projects/billing/decisions." The agent calls data_write:

data_write {
  "operation": "create",
  "name": "projects/billing/decisions",
  "about": "Decisions for the billing refactor",
  "value": { "decided": ["keep invoices immutable"], "open": ["proration"] }
}

Later, in Cursor or ChatGPT: "Read projects/billing/decisions from Tunc Orb." That agent calls data_read with operation get and the same name, and gets the same value back, with its revision and who saved it.

3. Name things so every agent finds them

  • Names are exact (up to 512 bytes, never normalized). Collections are just naming conventions, such as projects/<name>/... or contacts/<id>.
  • Every record and log has an about line (up to 160 characters) saying what it holds, so another agent can tell what it is before reading it.
  • Agents look before they create: data_read with operation list and a prefix shows what exists, and operation search finds literal text under a prefix (no regex).

See which agent wrote what

Each record carries its writer: the name of the connection that saved it, such as "Tunc Hub · 7F3A" for a Tunc Hub chat or the name you gave an API key. On your own store you can tell your agents apart at a glance.

Stay in control

Every connected app is listed under Agents & keys on your account (https://tunchub.com/account?tab=agents). Rename one, narrow it to read-only, or disconnect it; a disconnected agent is refused within a minute and your other agents keep working. Nobody else can see your store, and the website never shows the records themselves.

Free: 1 GB of storage shared by Tunc Hub, Tunc Art and Tunc Orb, with 50,000 Tunc Orb operations a day.