Skip to main content
GET
List MCP Tool Names

Response

200 - application/json

Successful Response

Subset of AllowedTool values that represent MCP servers.

Single source of truth for which tool names route to MCPs (Linear, Notion, ...) vs harness-provided tools (Read, Bash, ...). Values must stay aligned with the matching AllowedTool members.

The frontend reads this enum's members via the generated SDK (components['schemas']['McpTool']). Its own MCP_TOOLS list in egp-annotation/.../beta/build/custom/_api/constants.ts is asserted at compile time to be a SUBSET of this enum, so renaming or removing a member here fails the frontend typecheck. The reverse is deliberately not enforced: a name can exist here while the UI still hides it, which is how a server is staged before its OAuth flow is ready.

Like AllowedTool, this list is permissive by design. Presence here only means the API accepts the name; the golden agent's catalog decides whether it resolves, and MCP_TOOLS decides whether it is offered.

Available options:
Slack,
Linear,
GitHub,
Confluence,
Notion,
Datadog,
PagerDuty,
Salesforce,
Figma,
Granola,
Jira,
Gmail,
GoogleCalendar,
GoogleDrive,
GoogleDocs,
GoogleSheets,
GoogleSlides,
Snowflake,
Redash,
Tableau,
Metabase,
Gong,
ZoomInfo,
Clay