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

# Connect Claude or ChatGPT

*What you'll get: your own AI assistant (Claude or ChatGPT) able to read your Biodock analyses and results, and, if you allow it, organise files or start analyses.*

Biodock has an MCP server, the standard way AI assistants connect to other apps. Once connected, you can ask your assistant things like "Which of my analyses from last week found the most nuclei?" and it reads the answer from Biodock.

## Before you start

1. In Biodock, click your name at the top right, then **My Account**.
2. In the **AI features** card, turn on **MCP access**. It is off until you turn it on, and it only affects you.

If **AI features** isn't on your **My Account** page, MCP access is not available on your account yet. Contact <support@biodock.ai>.

## Connect Claude

In Claude, add a **custom connector** with these values:

| Field               | Value                              |
| ------------------- | ---------------------------------- |
| Server URL          | `https://app.biodock.ai/mcp`       |
| OAuth client        | **Use your own OAuth client**      |
| OAuth client ID     | `8YdH8wsIbG13FvpHjqGFvcqDGerIKG6f` |
| OAuth client secret | leave empty                        |

{% hint style="warning" %}
Claude selects **Register automatically** for the OAuth client by default. That option does not work with Biodock. Choose **Use your own OAuth client** and paste the client ID above. This is the most common reason a connection fails.
{% endhint %}

Then sign in to Biodock when Claude asks, and approve the access screen.

## Connect ChatGPT

ChatGPT connects to the same server with its own client details. Contact <support@biodock.ai> and we'll send them to you.

## What your assistant can do

When you first connect, Biodock asks you to approve **reading only**: your analyses, their results and your files. Your assistant can then find analyses, read measurements, compare groups and look at images.

Some requests change your account. The first time you ask for one, your assistant asks you to approve that kind of access separately:

* **Organise files**: rename, move, create folders and move items to the trash.
* **Write jobs**: start analyses, create populations and change which model version a project uses. Starting an analysis uses credits, exactly as it does in the app.

The two are separate, so you can let an assistant tidy files without letting it spend credits.

## Use it in a workspace

A connection uses your personal account by default. To work in a workspace instead, add the workspace to the server URL:

`https://app.biodock.ai/mcp?workspace=<workspace>`

Replace `<workspace>` with the name in your workspace's address: in `app.biodock.ai/w/rivera-lab/home` it is `rivera-lab`.

Workspace owners and admins can refuse AI connections in the workspace with **MCP connections** in **Settings**. Scripts using API keys are not affected. See [Workspace settings](https://docs.biodock.ai/workspaces/workspaces/workspace-settings.md).

## If it doesn't connect

| What you see                                     | What to do                                                                           |
| ------------------------------------------------ | ------------------------------------------------------------------------------------ |
| "Biodock MCP access is off for your account…"    | Turn on **MCP access** in **My Account**. The connection works as soon as it is on.  |
| "This feature is not available on your account." | MCP access isn't on your account yet. Contact support.                               |
| The connector fails right after you add it       | Check that **Use your own OAuth client** is selected and the client secret is empty. |


---

# 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.biodock.ai/assistant/connect-claude-or-chatgpt.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.
