Skip to main content
MCP connections give Delphina access to external services — GitHub, Notion, Slack, Linear, and others — through the Model Context Protocol.

​
Two ways Delphina uses a connection

  • On the fly, during a chat — the agent calls the service’s tools live while answering a question, for example searching GitHub issues or looking up a Slack thread. Nothing is stored; the agent reads what it needs, when it needs it. This works as soon as the connection is created.
  • As a knowledge source — during a knowledge update, the agent pulls content from the service and ingests it into your knowledge base as documented tables, metrics, and rules, available to every chat afterwards without calling the service again. This one is opt-in: it needs both a knowledge Usage and a knowledge pull prompt.

​
Add a connection

  1. Go to Org Admin > MCP Connections.
  2. Click Add Connection.
  3. Select a workspace, then provide the connection name, description, URL, and settings described below.
  4. Click Create.

​
Connection settings

​
Usage

Usage controls whether the agent can use a connection for knowledge work, analytics chats, or both. New connections start as Analytics only:
  • Analytics only — use the connection only for analytics chats. (Default for new connections.)
  • Knowledge & Analytics — use the connection for both knowledge work and analytics chats.
  • Knowledge only — use the connection only for knowledge work.
Usage decides which surfaces may reach the connection at all. Allowing knowledge work does not by itself onboard anything — that also needs a pull prompt.

​
Knowledge pull prompt

The pull prompt scopes what the agent ingests into the knowledge base from this connection — for example, “Pull all pages under the Metrics space” or “Pull the README and docs/ directory from the analytics repo”. First set Usage to Knowledge & Analytics or Knowledge only at Org Admin > MCP Connections — analytics-only connections are not listed as knowledge sources, so a new connection will not show up until you do. Then go to Context Layer > Sources and select the connection by name. (The prompt lives with the other knowledge sources rather than in Org Admin, alongside Tables, Query Users, and File Uploads.) Leaving the prompt empty disables the connection as a knowledge source — the Sources list shows it as Disabled — no pull prompt set.
A connection is onboarded only when its Usage includes knowledge and it has a pull prompt. Without a prompt nothing is ingested, but the agent can still call the connection’s tools live — in the guided knowledge chat always, and in analytics chats unless Usage is Knowledge only.
Be specific about scope. A vague prompt like “Pull our documentation” makes the agent guess at boundaries; naming the space, repo, or channel keeps each update predictable and fast. Each knowledge update re-pulls the content the prompt describes rather than fetching only what changed, so ingestion always reflects the latest snapshot — renamed, deleted, or rewritten pages are picked up on the next update.

​
Authentication

Auth Type determines how Delphina authenticates to the MCP server:
  • None — no credentials are required.
  • Bearer Token — send a bearer token with requests.
  • Custom Headers — send credentials or other values in request headers.
  • OAuth — authorize an account through the provider.

​
Token Binding

For OAuth connections, Token Binding controls whose authorization is used. Choose Per-user when each Delphina user should authorize with their own account. Those users see a Connect banner before they can use the connection. Choose Shared by workspace when one admin-owned OAuth grant should be used for everyone in the workspace. Token Binding cannot change after creating an OAuth connection.

​
Chat visibility

Chat Visibility controls privacy for new chats that use this connection:
  • Default — chats follow normal workspace visibility. Workspace members can see them.
  • Owner only after tool use — after the agent attempts a tool from this connection, only the chat owner can see that chat. Use this for connections that may expose sensitive information.
Changing this setting affects only new chats. Existing chats keep their current visibility.

​
Common connection setup

​
Attio

Add a connection with URL https://mcp.attio.com/mcp, Auth Type OAuth, your preferred Token Binding, and blank Advanced fields unless you need a pre-registered OAuth client. The agent can search and manage CRM records, notes, tasks, comments, meetings, emails, and reports according to the connected Attio user’s permissions.

​
GitHub

  1. Create a fine-grained PAT with read access to Contents, Issues, Pull requests, and Metadata.
  2. Add a connection with URL https://api.githubcopilot.com/mcp/ and the PAT as the bearer token.
The agent can then search code, read files, list issues/PRs, and get commit history from your repos. Start read-only; add write permissions only if you want the agent to create or update GitHub resources.

​
Google Workspace

Add a connection with URL mcp://internal/google-workspace, Auth Type None, and no token. Delphina recognizes this internal URL and configures Google OAuth automatically. After users connect OAuth, the agent can use Google Workspace tools for Calendar, Docs, Drive, Gmail, Slides, Sheets, and Tasks. Default scopes are calendar, documents, drive, gmail.modify, presentations, spreadsheets, and tasks.

​
Linear

Add a connection with URL https://mcp.linear.app/mcp, Auth Type OAuth, your preferred Token Binding, and blank Advanced fields unless you need a pre-registered OAuth client. The agent can find, create, and update Linear issues, projects, and comments according to the connected Linear user’s permissions.

​
Notion

Add a connection with URL https://mcp.notion.com/mcp, Auth Type OAuth, your preferred Token Binding, and blank Advanced fields unless you need a pre-registered OAuth client. The agent can read and write Notion workspace content according to the connected Notion user’s access.

​
Slack

Add a connection with URL mcp://internal/slack, Auth Type None, and no token. Delphina recognizes this internal URL and configures Slack OAuth automatically. After users connect OAuth, the agent can list readable channels, read channels and threads, and search messages. Slack enforces membership, so users can only read channels, DMs, and group DMs their Slack account can access.

​
Manage connections

  • Edit — click the pencil icon to update the name, description, usage, chat visibility, or auth details. You cannot change the URL after creation; delete the connection and create a new one to use a different URL.
  • Delete — click the trash icon.

​
Troubleshooting