> For the complete documentation index, see [llms.txt](https://docs.corpdev.ai/corpdev.ai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.corpdev.ai/corpdev.ai-docs/connect-an-mcp-client.md).

# Connect an MCP client

MCP lets an AI assistant use tools exposed by another application. CorpDev.Ai's in-app Analyst tools and its external customer integration are separate interfaces.

## Supported setup must match your deployment

External access requires an enabled workspace and a scoped CorpDev.Ai API key. Confirm the client package and transport supplied for your account before configuring it. Do not assume that a URL displayed in the app establishes a working remote MCP or OAuth service.

The external bridge represented by the current integration uses **stdio**: your MCP client launches a local process, and that process calls the public REST API. The setup below applies only if CorpDev.Ai has supplied that bridge to you. It does not imply a publicly available npm package or a remote HTTP transport.

## Configure a supplied local bridge

1. Obtain the supported bridge package and runtime instructions from your CorpDev.Ai representative.
2. Create a key for the intended workspace with only the scopes required by your tasks.
3. Configure your MCP client to launch the supplied bridge entry point.
4. Supply `CORPDEV_API_KEY` securely in that process's environment.
5. If needed, set `CORPDEV_API_URL` to `https://api.corpdev.ai`. This is the origin only; the bridge appends `/v1/public`.
6. Restart the client connection and try a read-only operation against a designated test workspace.

Do not paste the secret into an Analyst prompt or save it in a shared configuration repository. Follow your client's supported secret-handling mechanism.

## Permissions and tools

Tool groups include documents and jobs, attachments and exports, research, companies and people, lists and pipelines, AI Room, markets, usage and enabled automation operations.

A tool may be listed even when your key cannot execute it. The API checks scope, role, workspace enablement and credit availability at execution time. A tool list is not a grant of permission.

If a setup supports multiple workspaces, each workspace needs an appropriately authorized key. A workspace label selects a configured credential; it is not a way to override the tenant fixed by an existing key.

## Troubleshooting

* **Process fails to start:** check the supplied runtime and entry point, then confirm the environment variable is present without printing the secret.
* **401 or 403:** check expiry, revocation, scope, membership and workspace API access.
* **Tool succeeds but work is unfinished:** follow its returned job status; acceptance is not completion.
* **Remote URL does not connect:** confirm that remote transport is actually supported for your deployment before changing authentication settings.

See [API access](https://docs.corpdev.ai/corpdev.ai-docs/api-access-and-authentication) and [Errors and retries](https://docs.corpdev.ai/corpdev.ai-docs/errors-pagination-and-retries).