Skip to main content
The Delphina MCP server offers the tools below. Which ones your client sees depends on your role and on whether its connection has administrative access.

Everyday tools

Every member gets these. They act as you, so a tool returns exactly what you would see in the web app and nothing more — your workspaces, your chats, the knowledge you can already read. The administrative tools further down are separate and need administrative access.

Workspaces and setup

Asking a question

The normal flow is start_chat, then wait_for_turn, then get_turn_result.

Reading past work

Knowledge

These read your Context Factory knowledge base: the curated metrics, tables, notes, and rules the agent reasons over.
The knowledge base holds definitions, not data. To get a number, use start_chat — it already applies these definitions. Read the knowledge base directly when you want your own agent to reason over your definitions, for example to write SQL that matches how your team defines a metric.

Projects

Org admin tools

Organization admins get extra tools for the work they would otherwise do on Org Admin > Usage Limits and Org Admin > Users. The tools appear only for org admins whose connection has administrative access (see Administrative access); other members never see them, and the server checks admin status again on every call. Spend caps are monthly (calendar month, UTC) and in US dollars, measured against the same spend Usage Limits shows. A member’s own cap replaces the base cap for them, whether higher or lower. When a member reaches their cap, they can’t start new agent turns until the month ends, so lowering a cap can block people immediately. The tools tell the assistant to check with you before it changes caps or deactivates anyone. To use these tools with a token rather than OAuth, the token must carry the org:admin scope or be a token without scopes; see Token authorization.

Member profile tools

Org admins can read and change the profile details on Org Admin > Users that have no other tool: a member’s bio and secondary email. Each tool takes the member’s user ID from list_org_users, needs a connection with administrative access (see Administrative access), and acts only on members of your own organization. Workspace Developers with administrative access also see them, but only org admins can use them: Delphina refuses the call for anyone else.

Workspace membership tools

Org admins and workspace Developers can look up who belongs to the workspaces they administer. Like the org admin tools, these need a connection with administrative access (see Administrative access), and Delphina checks your permission for the selected workspace on every call.

Usage and settings tools

Org admins can read their organization’s usage report, settings, and seat limits. These tools need a connection with administrative access (see Administrative access) and act on your own organization. Workspace Developers with administrative access also see them, but only org admins can use them: Delphina refuses the call for anyone else.

Access tools

Org admins can see and change who in their organization may use MCP and API keys. One setting covers both, and a change takes effect on each person’s next request; existing tokens and keys are not deleted. System users and service accounts always have access. These tools need a connection with administrative access (see Administrative access) and act on your own organization.