Connectors
Give your AI new powers — GitHub, Slack, Postgres, Supabase, email, and more.
Connectors wire external systems into your project so your AI can read from
and act on them. Each connector handles its own credentials (sealed into the
vault) and, where it reaches the network, its own
egress allowlist entry. Build them as
Root Functions (custom HTTP integrations) or
mount an external MCP server with the mcp_server_install tool.
Two kinds of connector
| Kind | What it is | Example |
|---|---|---|
| MCP | Installs an external MCP server into your engine. Its tools appear to any connected AI client. | GitHub, Slack, Postgres, Supabase, Brave, Google Maps, Filesystem, Browser, Memory |
| Function | Deploys a Root Function that calls an external API — your key stays sealed and the call is egress-gated. | Resend (email) |
What "Connect" does
When you connect a connector, the Console runs up to three steps:
Seal its secrets
Any API keys you enter are sent to the gateway, sealed (libsodium sealed box), and stored as ciphertext. Plaintext is never persisted and never returned — see Secrets encryption.
Add egress (function connectors)
A function connector adds the domain it needs (e.g. api.resend.com) to the
project's egress allowlist so the engine is permitted
to reach it — and nothing else.
Install the MCP server or deploy the function
- MCP connectors call
POST /api/v1/ws/{ws}/mcp-servers, which mounts the external server live and notifies connected clients (tools/listChanged). - Function connectors deploy a Root Function via
PUT /api/v1/ws/{ws}/functionsthat reads the sealed secret fromctx.env.
Secrets inject at spawn
Secrets are injected into the engine container as environment variables when it starts. A secret added while the engine is already running takes effect after the next engine (re)start — there's no live secret reload today.
Common integrations
Examples you can build today. For MCP server specs and transports, see the MCP integration guide.
- GitHub · Slack · Postgres · Supabase · Brave Search · Google Maps · Filesystem · Browser (Puppeteer) · Memory · Resend (email)
MCP connectors need Node in the image
MCP connectors run via npx, so the engine container ships Node and Python.
Function connectors don't — they run inside the engine's own V8 isolate.