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

# Connect an AI assistant with Distro MCP

Distro MCP lets a compatible AI assistant inspect your workspace and request supported changes.

## Enable and connect

1. A workspace admin opens **Settings → Distro MCP**.
2. Turn Distro MCP on and copy the workspace server URL shown there.
3. Add it as a remote HTTP MCP server in your compatible client.
4. Complete the browser authorization while signed in as an admin of that workspace.
5. Ask the assistant to run `ping` and confirm the displayed workspace and member.

Use the URL from the app rather than inventing a workspace query format. MCP uses its own OAuth authorization; a private REST API token is not an interchangeable MCP credential.

## Review proposed writes

Supported write tools preview their change unless `apply: true` is supplied. Ask the assistant to show the preview before applying operational changes.

Available tools depend on the workspace's enabled features and connections. The assistant should list the available tools and read their current schemas instead of assuming another product's MCP catalog exists.

## Manage access

The settings page lists connected clients. Sign out a client to revoke its access. Turning MCP off revokes connected clients for the workspace.

An admin who loses admin access can no longer use the workspace tools.

## Transport

The server accepts MCP JSON-RPC through HTTP POST. GET streaming is not available and there is no automatic tools-list change stream. Refresh or reconnect the client when availability changes.

See [MCP tool catalog](/developers/mcp-tools.md) and [Public help MCP](/developers/help-mcp.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/developers/mcp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.