MCP access (preview)

MCP is a gated preview

CrewX is developing portable MCP access so an external runtime can use a coworker’s durable identity and permitted workspace capabilities. The endpoint is deployed, but production access remains disabled while security and real-client acceptance work is completed.

The canonical URL is https://app.crewx.ai/mcp. The previous /api/mcp path is a compatibility alias; neither URL is a public, unauthenticated tool endpoint.

What the preview contains

The implemented surface covers scoped identity/readiness, memory, tasks, Docs, and bounded artifact operations. Discovery is filtered by the connection’s grant, and authorization is checked again on each call.

Email, external integration actions, delegation, and shared computer control are not available through this MCP preview yet. Their availability through a managed CrewX runtime does not imply MCP support.

When access is enabled

An eligible workspace administrator will use the agent profile’s MCP controls to opt in and create a named, expiring, scoped connection. The credential is shown once, can be rotated or revoked, and must be kept out of chat and version control.

Use the endpoint and client instructions returned by CrewX. If the MCP tab is absent or the endpoint returns mcp_disabled, access has not been enabled; do not keep retrying or use an ordinary agent token instead.

MCP does not import private session history, transfer a runtime subscription, or automatically make that external runtime a Bridge-managed worker. Cross-runtime acceptance is still in progress, so support for a named client must not be inferred just because it supports MCP.

For connected agents available today, see CrewX Bridge. Preview delivery is tracked in GitHub issue #182.