Synap
Download

Ecosystem

Use your pod from the AI you already use.

One Synap connector for Claude, ChatGPT, Cursor and other clients that speak MCP. Pick yours for its setup guide.

Pick your AI

  • Claude Code

    Your pod as ambient tools in the terminal agent.
    Expected to workWith the Synap Cloud connector

  • Cursor

    Build with your pod's records, decisions and docs in context.
    Expected to workOne-click install

  • VS Code

    Your pod in Copilot's agent mode.
    Expected to workOne-click install

  • Windsurf

    Cascade reads and writes your pod as it works.
    VerifiedWith the Synap CLI

  • Codex

    OpenAI's coding agent, with your pod as context.
    Expected to workDirectly to your pod

  • Zed

    Your pod as a context server in Zed's agent panel.
    VerifiedWith the Synap CLI

  • Gemini CLI

    Google's terminal agent with your pod as a tool server.
    Expected to workWith the Synap Cloud connector

  • OpenCode

    Open-source terminal agent, connected in one command.
    VerifiedWith the Synap CLI

Don't see your client?

If it speaks MCP, it should work. Add the Synap Cloud connector URL — or ask the CLI for a direct pod URL.

Setup for any MCP client →

Two ways to connect. Start with the first.

Synap Cloud connectorRecommended

https://api.synap.live/mcp

One sign-in with your Synap account. Works in any MCP client that supports remote servers — including the web apps.

  • Works in claude.ai, ChatGPT, Le Chat — anywhere that needs OAuth
  • Every pod you own, behind one identity
  • Search and install from the Marketplace, from chat
  • No keys to copy, rotate or leak

Direct pod connectorSelf-hosting

https://<your-pod>/mcp

Talks to one pod with no Synap account in the loop. Set up by the CLI with a dedicated agent key.

  • No dependency on Synap's servers
  • The pod's full tool surface
  • Desktop and terminal clients, via synap mcp connect
  • Web AIs only if your pod is public over HTTPS — set up by hand
Why are there two connectors?

Your Data Pod is yours: it has to keep working if Synap disappears. So every pod speaks MCP on its own — that is the direct connector, and it will always exist.

The Cloud connector is a layer on top. Because it knows your Synap identity, it can do what a single pod cannot: sign you in once across all your pods, satisfy the OAuth that web AIs require, and connect you to what is shared between pods — the Marketplace, the packages you publish, and the network features we add over time.

Your data does not move into the Cloud connector. It brokers the connection; your pod still answers every request and still reviews every consequential change.

Bring your services in

Sync the tools you already use into your pod. The first sync arrives as a proposal you review.

  • Google Workspace

    Gmail, Calendar, Drive and Contacts — one sign-in. The first sync arrives as a proposal for your review.
    Live

  • GitHub

    Repositories, issues and pull requests.
    Planned

  • Notion

    Pages and databases as structured records.
    Planned

  • Linear

    Issues, projects and teams.
    Planned

  • Slack

    Channels and threads, searchable in your pod.
    Planned

Keep going