Connect an MCP client

The recommended way to connect a workspace is the tenant HTTP endpoint, authenticated with the MCP key issued specifically for that workspace. The stdio bridge can use that same HTTP endpoint and workspace key. Its separate local database mode is reserved for installation administrators.

Connect over HTTP

1. In the intended workspace, open Integrations and generate an MCP key. Copy it when it is shown; keep it private.
2. In an MCP client that supports Streamable HTTP and Bearer authentication, add the endpoint below using your actual domain and tenant slug.
3. Configure the workspace key as the Bearer credential using the client's supported authentication controls. Do not put the key in the URL.
4. Enable the connection and ask for a bounded read, such as the current Today queue. Verify that the result belongs to the intended workspace.

https://<your-domain>/api/public/<tenantSlug>/mcp

Client configuration screens differ. Use your client's current MCP instructions for its connection fields. The endpoint and workspace credential above are the Command Center settings it needs.

ChatGPT compatibility

Use ChatGPT’s current plugin connection controls and a separately configured OAuth connection. A workspace MCP API key is not the credential for that OAuth flow. Account eligibility and supported clients can change; check OpenAI’s connection guide and authentication requirements.

ChatGPT web requires a separately configured OAuth connection. To use the registered workspace tools, an installer follows the workspace MCP OAuth guide. The separate Site Studio connection below is scoped to the installation website and does not expose ordinary workspace tools.

The workspace OAuth endpoint is https://<your-domain>/api/public/<tenantSlug>/mcp/oauth. An active workspace admin consents for 30 days and can revoke access in Integrations → Manage workspace OAuth connections. Available tools still follow the module, connection and approval rules below. Verify one read, one proposal and its separate approval in the intended workspace before relying on the connection.

Choose a tool list

For installation-wide website editing from ChatGPT, use the separate Site Studio connection. It requires owner-approved OAuth setup and limits execution to website commands. The workspace key described on this page keeps its existing approval boundary.

Append ?profile=ops to the workspace endpoint for the Daily profile, or ?profile=core for a smaller set of daily reads and discovery tools. Use ?profile=full or the bare endpoint for the complete registered list. Existing bare endpoints retain the full list.

Profiles change what the client loads initially. They do not grant permissions or disable other registered operations. Discovery tells the client which other operations are available. If your MCP client needs the input definitions for an omitted tool, reconnect with the full profile. Bundle activation returns tool names, while tools/list continues to return the selected profile. Accelerate’s command host loads activated definitions from the shared registry. Execution still checks the workspace, module, connection and approval rules. If a client cannot load the full list, reconnect using the smaller profile and verify the same bounded read.

Understand what the connection permits

Available tools depend on module and connection requirements. Read tools return bounded workspace context. Integration-key connections can stage supported changes for approval. An authenticated member OAuth connection may execute a covered routine internal change under a current standing permission on named records, allowed fields, daily limits and expiry. The client cannot approve its own proposal or permission change through MCP.

A confirmation shown by the external assistant does not replace the Command Center's approval decision.

Connect a stdio client to the workspace

Set REVENUE_OS_MCP_URL to the tenant HTTP endpoint and MCP_API_KEY to its existing workspace key when launching scripts/revenue-os-mcp.ts. This bridge uses the same workspace authentication, tool discovery and approval rules as HTTP. It does not need a Supabase service-role credential. Follow the MCP setup guide for the complete client configuration.

Without the URL, the runner retains its separate installation-owner database mode. That mode uses the application's system workspace context. Use it only when you administer the installation and have verified its database and workspace scope.

Workspace requests reject malformed or oversized JSON and invalid UTF-8. Tools and their availability are refreshed against live workspace and module state before discovery or invocation. Revoked membership stops session-bound tool access. Browser integrations with a different origin require an installer-configured exact origin allowlist.

Troubleshoot the connection

Symptom	Check
No tools appear	The connection is enabled and the client supports this transport
Invalid or missing tenant key	The credential is sent as Bearer auth and belongs to the URL's workspace
A tool is unavailable	Its module and required provider connection are enabled and ready
The host cannot be reached	The domain resolves and the deployment is reachable from the client

An endpoint responding to a health request does not prove an authenticated tool call will work. Verify a read before trying to stage a change.

Example: connect a daily operations assistant

Maya wants an external assistant to inspect Northline's current priorities without changing records.

1. Generate the MCP key in Northline's Integrations screen and configure the tenant HTTP endpoint in the client. Use ?profile=ops for the Daily tool list.
2. Ask: “Read this workspace's Today queue. Show the linked records and explain which entries need a decision. Do not prepare or apply changes.”
3. Check that the returned business and record links belong to Northline. If they do not, disconnect and check the workspace URL and key before continuing.
4. For a later supported change, request a proposal and review it inside Command Center's Approvals. Inspect the execution result after your approval.

For example, an assistant saying “I prepared the update” means you should look for its pending proposal. It does not mean the record changed. If the smaller tool list omits a needed operation, ask the assistant to discover it; your permissions and module settings still decide whether it is available.

Delegate work from a connected agent

An authenticated member connection, including workspace OAuth, can preview and start ordered work, read its progress and control future steps through the same tools as Ask AI. A workspace bearer key represents an integration, not a requesting member, so it cannot start member-owned delegation or grant internal permission.

A pending proposal returns a focused, authenticated review link for its tenant and exact action. Open it to make the human decision. An external agent cannot approve its own proposal. After approval, read the actual receipt; permission, membership and freshness checks still apply at execution.

Report reads and exports

Ask for a Revenue or Analytics summary, then choose a narrower section or follow nextOffset for additional drilldown rows. Report tools share the dashboard services and disclose incomplete sources. JSON and CSV exports return the requested section or page, with filters and quality information; the client can save that content. Recorded won value and forecasts do not establish collected cash.

Use get_admin_operation_coverage to find an exact supported tool and inspect its reviewed mapping. Universal administration, including separately scoped founder operations, remains in progress. A registered tool still checks permissions, module state, source availability and relevant providers when it runs.

What to check

Confirm the workspace identity with a read, then inspect the exact proposal or current standing permission for a change. Keep pending, partial and unavailable outcomes visible, and rely on the saved service receipt for what actually happened. Verify installation-level access separately from workspace access.