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

# Connect an MCP client

Use the remote endpoint:

```
https://getminds.ai/mcp
```

OAuth is the preferred authentication method when the client supports it. For clients that accept custom headers, create a Minds API key under **Settings → API Keys** and pass it as a bearer token.

> **Security note:** Treat a Minds API key like a password. Do not commit it to a repository, paste it into public logs, or put it in documentation.

## ChatGPT

1. Open **Settings**.
2. Open **Connected Apps**.
3. Add `https://getminds.ai/mcp`.
4. Complete OAuth authorization.

Panel results can render as interactive widgets inside ChatGPT.

## Claude and Claude Desktop

1. Open **Customize → Connectors**.
2. Add `https://getminds.ai/mcp` as a remote connector.
3. Complete OAuth authorization.

For Claude Code with an API key:

```bash
claude mcp add --transport http mindsai https://getminds.ai/mcp \
  --header "Authorization: Bearer minds_YOUR_API_KEY"
```

## Cursor

1. Open **Settings → MCP**.
2. Add `https://getminds.ai/mcp`.
3. Complete OAuth authorization when prompted.

## Google Antigravity

Install the public plugin from GitHub:

```bash
agy plugins install https://github.com/minds-ai-co/minds-mcp
```

Antigravity discovers OAuth automatically from the remote MCP endpoint. Complete authentication in **Settings → Customizations**, then confirm that `minds` appears under `/mcp`.

For a manual connection, add the following to `~/.gemini/config/mcp_config.json` or the current workspace's `.agents/mcp_config.json`:

```json
{
  "mcpServers": {
    "minds": {
      "serverUrl": "https://getminds.ai/mcp"
    }
  }
}
```

Gemini CLI remains supported for Google Cloud enterprise and API-key users. Its legacy extension is still available from the same repository.

## ChatGPT and Codex Plugins

Minds is packaged as a shared ChatGPT and Codex plugin in this repository. Until the public directory review is complete, add `https://getminds.ai/mcp` as a developer-mode MCP connection and complete OAuth authorization.

## VS Code, Windsurf, Langdock, and Open WebUI

Add `https://getminds.ai/mcp` as a remote MCP server. The exact configuration surface differs by client; use OAuth where available and a bearer API key only when the client supports secure custom headers.

[Open the maintained setup guide](https://getminds.ai/mcp/setup?utm_source=content\&utm_medium=content\&utm_campaign=content-seo-mcp-reference\&utm_content=mcp-docs-connect)

## Confirm the connection

Ask the client to list the Minds tools. A successful connection should expose audience, panel, study, export, and research-method operations. Tool schemas are described by the server at runtime; do not hard-code parameters from an old chat session.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://minds-1.gitbook.io/minds-mcp/connect.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.