This feature is in beta. Please contact your administrator for access. GA is coming soon.
How it works
Delphina exposes an MCP server using the Streamable HTTP transport. MCP clients connect to it and gain access to tools for starting chats, sending messages, and retrieving results — the same capabilities available through the web app and Slack. Delphina uses OAuth for MCP authorization when your client supports it. OAuth is preferred because it is usually simpler to set up and more secure: supported clients can handle the browser-based sign-in flow for you, and you do not need to copy or store a long-lived API key in client configuration. If your MCP client does not support OAuth, use API key authorization instead.Configure Delphina MCP
In Delphina, go to Settings > Connect to Delphina MCP. The page includes setup tabs for General, Claude Code, Claude Desktop/Cowork, Codex, and Cursor.General
Use this MCP server URL for any MCP-compatible client:Claude Code
Choose an installation scope in Delphina:- User (
--scope user) — available in all projects for the current user. - Local (
--scope local) — available only in the current project directory.
--scope local instead if you selected Local.
Claude Desktop/Cowork
In Claude Desktop/Cowork, go to Customize > Connectors > Add custom Connector, then paste the Delphina MCP server URL:Codex
Add the Delphina MCP server:Cursor
In Delphina, use the Cursor tab to open the Cursor install link. If the link does not open Cursor, create or edit~/.cursor/mcp.json for global setup or .cursor/mcp.json for project setup, then paste this JSON:
API key authorization
OAuth is preferred because it is usually simpler to set up and more secure than copying a long-lived API key into client configuration. If your MCP client does not support OAuth, go to Settings > Connect to Delphina MCP > General, expand API Key Authorization, and copy the Authorization Header value. Use that value as theAuthorization header in your MCP client configuration: