MCP hub

The MCP hub is one registry of Model Context Protocol servers that Synergoi mounts into every provider session — so a database tool, a browser, or your company's internal API is available to Claude, Codex, Grok, Cursor, Antigravity and local models alike, configured once.

Built-in connected apps

Settings › Integrations also offers Linear, Google Drive and Microsoft 365 as built-in connections — no server to register and no JSON to write. They enter this same hub, so every provider sees them. Full details, capabilities and the data boundary are on Connected apps.

Registering a server

1. Open Settings › Integrations

   Expand Custom MCP tools to manage registered servers, their transport (stdio command or HTTP URL), and provider compatibility.

2. Register server

   Give it a name and either a command to spawn or an HTTP endpoint. Secrets the server needs (an API key, a connection string) go in Store environment secret — they are kept in the app's data folder, injected at spawn time, and never written into a provider's config file.

3. Let the next session pick it up

   Registry changes mount when the next eligible session opens; running sessions keep the set they started with.

Provider compatibility

Not every CLI speaks every transport. The Provider compatibility disclosure shows, per provider, which of your servers will mount and why one won't; Session MCP shows the live conformance check for the session you have open.

Tools and approvals

MCP tool calls go through the same approval broker as shell commands: under Ask they ask, and a remembered rule can allow a specific tool on a specific server.

Export to native CLI configs

If you also use the CLIs outside Synergoi, Export to native CLI configs writes the registry into each vendor's own MCP config format so both worlds stay in sync.