Docs menu
Connectors
Every connector the gateway supports, how sign-in works per tool, and how to attach any MCP server from the directory or your own.
Last updated Aug 20, 2026
A connector is a service behind the gateway. You connect it once under Connected tools, sign in once for that service, and every agent you own can use its tools from then on. Credentials are stored encrypted and every connection can be revoked at any time.
The curated catalog
| Connector | Sign-in |
|---|---|
| Tulimoa Directory | Built in, none needed. Preinstalled for everyone. |
| GitHub | OAuth, or a personal access token as fallback |
| Linear | OAuth |
| Notion | OAuth |
| Sentry | OAuth |
| Atlassian (Jira, Confluence) | OAuth |
| Granola | OAuth |
| Pylon | OAuth |
| TinyFish | OAuth |
| Wix | OAuth |
| Exa | None, works immediately |
| Hugging Face | API key |
| Langfuse | API key pair |
| Polar | API key |
| TrustMRR | API key |
The catalog grows continuously; the live list is always in Connected tools. Missing a service you need? Tell us via Help.
How sign-in works
- OAuth. You click connect, approve at the service, done. The gateway stores the tokens encrypted and refreshes them automatically.
- API key. You paste the key once; the gateway encrypts it and sends it only in the moment of a call.
- None. Public servers connect instantly, nothing to configure.
Per-tool switches
Every connector exposes its tools individually in Connected tools. Switch off the ones your agents should not use; they disappear from the agent's tool list without disconnecting the service. Handy for keeping destructive tools out of reach or for slimming a noisy connector down to the three tools you actually use.
Attach any MCP server from the directory
Beyond the curated catalog, every approved listing in the directory that runs its own MCP server can be attached to your gateway straight from Discover. Servers without auth attach instantly; servers that want an API key ask you for it once. Servers that only speak OAuth cannot attach through this bridge; those we bring into the curated catalog instead.
Bring your own MCP server
Any MCP server that speaks streamable HTTP on a public https endpoint can ride the same bridge:
- Submit it to the directory with its MCP endpoint. Review usually takes about a day.
- Once approved, attach it from Discover like any other listing, without auth or with your API key.
- If your server needs OAuth, contact us via Help and we set it up as a curated connector.
For safety the gateway only talks to public https endpoints; internal or private addresses are rejected.