Connect an MCP (Model Context Protocol) server to let Delta’s agents use tools from external services.
Connect an MCP server
Delta connects to remote HTTPS MCP servers with OAuth authentication or no authentication.
- Sign in to Delta and open Settings > MCP in the desktop app.
- Make sure the switch at the top of the MCP settings page is on.
- Click on Search providers or enter an MCP URL. Select a provider, or paste your server’s MCP endpoint URL and choose Use custom MCP server.
- If the server requires authorization, choose Sign in beside it and complete authorization in your browser.
- Wait for the server’s status to show Connected. Its tools are available to the agent on your next turn.
Authentication
Delta supports MCP servers with these authentication options:
- No authentication.
- OAuth 2.1 for all servers that support dynamic client registration.
- OAuth through apps manually registered by Delta, including Slack, GitHub, and Figma.
Local MCP servers and remote servers that require manually supplied bearer
tokens or API keys (such as x-api-token headers) are not supported.
Manage connections
- Choose Reauthorize to authorize an OAuth connection again.
- Choose Remove to remove a configured server from Delta.
- Turn off the switch at the top of the MCP settings page to stop offering configured MCP tools to new agent turns without removing the servers.
Troubleshooting
A server needs authorization
For Authorization required, choose Sign in. For Reconnect required, choose Reauthorize and complete the browser flow.
A custom server cannot connect
Check that you entered the MCP endpoint, that it is publicly reachable over HTTPS, and that it uses one of the supported authentication options listed above.
What’s next
- Skills teach agents reusable workflows, including how to use connected tools.
- Agentic Safety covers the risks of giving agents access to tools.