Arc0 MCP

Discover and execute authorized tools through one authenticated MCP endpoint.

Arc0 gives an agent access to the tools enabled for one organization, project and person. Tools can use that person's connected accounts, approved business credentials, public access or Arc0-provided access. Discovery and execution share the same permissions.

Endpoint and authentication

Copy the endpoint from Arc0 MCP in your dashboard. The API serves /mcp; the local runtime uses http://localhost:4312/mcp. A scoped endpoint can also use /mcp/p/{projectId}/u/{endUserId}. These are Arc0 internal IDs, not your external user IDs. Its path must match the authenticated identity; changing the URL cannot select another user.

OAuth is the default for interactive clients. Better Auth manages sign-in, client registration, PKCE, consent and refresh. Choose a workspace and review the client and selected identity before allowing access. Account switching does not change an existing agent authorization. Revoke that authorization from Arc0 MCP when it is no longer needed.

For clients without OAuth support, create a self-bound API key and send it in the x-api-key header. Unbound business management keys cannot authenticate to MCP. An execution-only key cannot create connection links; that also requires connect permission. Bearer tokens are reserved for OAuth. Invalid OAuth credentials never fall back to an API key.

When requesting a hosted connection link, manage_connections accepts an optional authMethod: oauth, api_key, or basic. The provider must support that method; GitHub supports OAuth and personal access tokens, while basic authentication is available only with the local test provider. Credentials are entered on the hosted page, never passed as MCP arguments.

This authenticates the agent to Arc0. Connecting Arc0 to GitHub or another provider is a separate consent and credential flow.

Transport

The current server uses the official MCP TypeScript SDK 1.32.1 with Streamable HTTP. Its latest supported protocol is 2025-11-25; client and server negotiate a supported version. It does not claim the later 2026-07-28 transport profile.

The transport is stateless: clients send JSON-RPC requests by POST. There is no persistent GET event stream or resumable transport session. Execution IDs and idempotency keys provide application-level result retrieval and retry safety.

Meta tools

ToolPurpose
search_actionsFind a short authorized list; request an exact action to obtain its input schema.
manage_connectionsList enabled apps and your own accounts, check status, obtain hosted connect/reconnect links, or revoke your own connection after confirmation.
arc0_helpSearch end-user documentation about connecting, revoking access and data handling.
execute_actionExecute an exact action version with arguments and a stable idempotency key.
get_executionRead the status and retained result of your execution.

Search uses PostgreSQL lexical ranking with English stemming. App filters, project settings, active identity and policy apply before results are returned. Advanced semantic ranking is not enabled. A discoverable tool can still report connection_required, connection_ambiguous or billing_required; discovery never grants access by itself.

Request the schema with an exact action lookup before executing it. Project versions are pinned, and old versions fail closed when their adapter is unavailable. An administrator can select the currently published version explicitly from the tool's configuration.

For a small, fixed integration, the server also supports an operator-configured selection of individual tools with version-qualified names, such as github__get_public_repository__v1. The same authorization and execution checks apply. This option is not an unrestricted export of the whole catalog.

Connection self-service derives the user and project from the authenticated binding. manage_connections supports list, list_apps, status, connect, reconnect and revoke. Status, reconnect and revoke require your connectionId; revoke also requires confirm: true after you confirm disconnecting that account. Runtime keys need connect permission for connection mutations. Because the tool includes revoke, its MCP annotation marks the entire tool as destructive. See Manage your connections with MCP for the end-user guide.

Execution and approvals

Keep one idempotency key for one unchanged request. Never generate a fresh key merely because a provider write timed out. Retrieve the receipt and reconcile uncertain outcomes. An ask policy holds the exact request for human approval; the agent cannot approve its own request. Result retrieval rechecks current access and respects retention.

See MCP clients for setup and SDKs for direct API access.

Shared group access

Embedded callers may supply an explicit groupId to search_actions and execute_action. Arc0 checks current membership and the group's status before discovering shared tools or dispatching work. A group grant is considered only when that group is selected; removing membership or revoking the grant removes access. Direct accounts do not accept group context. Connection self-service lists only accounts owned by the authenticated individual. Group-owned and granted/shared accounts stay invisible to manage_connections, which rejects groupId for every operation. Hosted setup links bind to that individual.

On this page