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

# Read-Only MCP API

Connect external tools to investigate your Middle data

The Read-Only MCP API lets you connect external tools, such as ChatGPT, to Middle. These tools help you investigate records, understand workflows, and troubleshoot integration issues.

{% content-ref url="/pages/rIZ4psMH9obe7LqyK7kI" %}
[Connect ChatGPT](https://docs.middle.app/middle-docs/ai/connect-chatgpt.md)
{% endcontent-ref %}

{% content-ref url="/pages/VtLBCYupVwpWlK7bvZuL" %}
[Connect Claude](https://docs.middle.app/middle-docs/ai/connect-claude.md)
{% endcontent-ref %}

## What you can do

A connected tool can review your records, workflow configuration, sync and execution logs, and Middle's documentation. For example, you could ask why a contact didn't reach your CRM or why a workflow used an unexpected value.

Access is currently read-only. Connected tools cannot edit workflows, run actions, or re-sync data.

## Control access

An Organization Owner registers and approves a tool under **More → API Clients**. Each user then authorizes it using their own Middle login. The tool can only read data that user is allowed to access.

You can review your authorizations and select **Revoke access** under **My Session → User settings → API clients using your credentials**. Organization Owners can review authorizations, revoke individual access, or disable a client for everyone from **More → API Clients**.

## Get started

Follow [Connect ChatGPT](https://docs.middle.app/middle-docs/ai/connect-chatgpt.md) for setup instructions. Other compatible MCP clients can connect to Middle's investigation tools too.


---

# 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 by asking a question.

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

```
GET https://docs.middle.app/middle-docs/ai/api-clients.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 `automate deployments from our CI pipeline` 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.
