MCP servers · Talyn docs
MCP servers
Connect Linear, Sentry, Stripe or your own MCP server. Allow all repositories or only selected ones. The keys stay with Talyn and never enter the sandbox.
Connect an MCP server, and the agents in your sessions, fix runs, reviews and scheduled automations get its tools. For example, connect Linear and the agent can read the issue it is working on. Connect Sentry and it can read the stack trace.
This page is about giving Talyn's agents more tools. To use Talyn itself from Claude Code or Cursor, see Talyn MCP server.
Connect a server
- Open Settings > MCP servers in the desktop app. In the web app, go to app.talyn.dev/mcp-servers, or search for "MCP servers" in the command palette.
- Select Add a server.
- Pick a server from the catalog, or paste the address of any other server.
- Sign in or paste a key. See below.
- Select Connect.
- Choose whether all repositories or only selected repositories can use it.
- Choose the tools your agents can use.
- Select Save.
The catalog includes Linear, Sentry, Notion, Jira and Confluence, Asana, Stripe, Supabase, Neon, PostHog, Vercel, Netlify, Cloudflare, Figma, Slack, Context7, Hugging Face and more. For a server that is not in the catalog, paste its address. Talyn checks the address and finds how it signs in.
Talyn supports remote MCP servers over HTTP. Use a public server or an exact workspace private route. For a private server, connect the workspace connector first. Add its exact hostname and port in private route settings. Use HTTPS. OAuth endpoints on other private hosts need their own routes. Setup does not require a sandbox. The address cannot hold a username, a password, a query string or a #fragment.
Sign in or paste a key
Each server uses one of these:
- Sign in with OAuth: select Connect account and sign in in your browser.
- No key needed.
- API key (Bearer), API key in a header, or API key in the URL: paste the key.
- A username and password.
Talyn stores keys encrypted. The sandbox never receives them: the agent calls the server through Talyn, and Talyn adds the key to each request on the way. An agent that reads a hostile file and tries to leak your key has no key to find.
For Stripe, use a restricted key, so that the agent can do only what you allow.
Name a server
Talyn names a new server from the catalog or from its address. To change the name, open the server and go to Name:
- Display name is the name that you see in Talyn. It can contain spaces and capital letters, for example "Linear (work)".
- Identifier is the name that agents use to reach the server. Use lowercase letters, digits and hyphens. Each server in a workspace must have a different identifier.
The identifier github is not allowed. The sandbox uses that name for its own GitHub access. Talyn turns capital letters in an identifier into lowercase letters.
Select Save to keep the change. A session that is running keeps the old identifier until its sandbox restarts.
Choose the tools
After Talyn connects, it lists the server's tools. Choose which ones your agents can use:
- All tools (including any this server adds later).
- Only the tools you tick.
- None. The server stays connected, with no tools.
Choose repositories
Each server is available to all repositories by default. This default also includes repositories that you add later.
Select Only selected repositories to limit access. Then select each repository that can use the server. Repository-free threads cannot use a limited server.
Turn a server on or off
Each server has an On/Off switch. A server that is off is not given to any run.
A scheduled automation can use every server that is on, or a set you choose for that automation.
Remove a server
Select delete on the server. Talyn also deletes its stored key. Runs that already started keep the access they had.
Plans
You can connect as many MCP servers as you like on every plan.