> 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/connect-claude.md).

# Connect Claude

Connect Claude to Middle by registering Claude as an approved API client in Middle, then adding Middle as a custom connector in Claude.

These instructions cover **Claude on the web, Claude Desktop, and Cowork**. They adapt Middle’s documented setup to Claude’s OAuth settings; I haven’t tested the connection end to end.

Middle’s MCP access is **read-only**: Claude can investigate records, workflows, and logs using the connected user’s permissions. It cannot edit workflows, run actions, or re-sync data. [Middle documentation](https://docs.middle.app/middle-docs/api-clients)

{% stepper %}
{% step %}

### **Register Claude in Middle**

Sign in to Middle as an **Organization Owner**, then open **More → API Clients → Register API client**. Choose **Use a metadata document** and enter:

```
https://claude.ai/oauth/mcp-oauth-client-metadata
```

Select **Load metadata**, review Claude’s name, website, and redirect URLs, then select **Approve and enable**. Confirm that the client’s status is **Enabled**.
{% endstep %}

{% step %}

### **Add Middle as a custom connector in Claude**

For an individual account, open **Customize → Connectors → Add custom connector**. For Team or Enterprise, an authorized owner first adds it under **Organization settings → Connectors → Add → Custom → Web**.

Enter the following settings:

| Setting                  | Value                                         |
| ------------------------ | --------------------------------------------- |
| Name                     | `Middle`                                      |
| MCP server URL           | `https://example.middle.app/oauth/mcp/`       |
| Authentication, if shown | **Sign in now**                               |
| OAuth client, if shown   | **Use Claude’s published identity**           |
| Client ID and secret     | Leave blank when using the published identity |
| Request headers          | Leave blank                                   |

Replace `example` with your Middle installation’s subdomain and **keep the final slash**. For example, Your Gym would use `https://yourgym.middle.app/oauth/mcp/`.

Finish by selecting **Add**. Claude’s dialog varies by account; some versions show **Advanced settings** instead of separate authentication steps.&#x20;

{% embed url="<https://claude.com/docs/connectors/custom/add-unlisted>" %}

{% endstep %}

{% step %}

### **Authorize your Middle account**

Select **Connect** beside Middle if authorization does not start automatically. When Middle opens, sign in and complete any authenticator check. On **Authorize access**, verify the client and signed-in email, then select **Authorize**.

{% hint style="info" %}
Each person connects using their own Middle login. The owner’s approval does not grant everyone the owner’s data access. [Middle authorization instructions](https://docs.middle.app/middle-docs/guides/connect-chatgpt)
{% endhint %}

{% endstep %}

{% step %}

### Enable Middle and test it

Open a Claude conversation, select **+ → Connectors**, and enable **Middle**.

Try:

> Use Middle to list the accounts I can access.

Then try a specific investigation:

> In \[account name], investigate why \[member email] did not receive points for their \[date] check-in. Review the record, workflow configuration, and execution logs. Explain what happened and link to the relevant Middle pages.
> {% endstep %}
> {% endstepper %}

If connection fails, confirm that the Middle API client is enabled and the server URL ends in `/oauth/mcp/`. For a redirect mismatch, Claude’s hosted apps use exactly `https://claude.ai/api/mcp/auth_callback`.

To disconnect later, open **My Session → User settings → API clients using your credentials** in Middle and select **Revoke access** for Claude.


---

# 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/connect-claude.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.
