Minds · MCP compatibility field guide

Remote MCP server · Compatibility reference

Connect once.
Research anywhere.

A practical field guide for connecting Minds to MCP-capable assistants, with a live reachability check against the canonical remote endpoint.

Connect Minds Technical reference

Client matrix

Six routes.
One endpoint.

Client interfaces differ, but each route points to the same public Minds MCP service. OAuth is preferred where the client supports it.

ClientTransportAuthenticationConfiguration route
ChatGPT Remote connector OAuth 2.1 Settings → Connected apps
Claude Remote connector OAuth 2.1 Customize → Connectors
Claude Code Streamable HTTP API key header claude mcp add
Cursor Streamable HTTP OAuth or API key MCP settings
VS Code Streamable HTTP OAuth or API key MCP server config
Windsurf Streamable HTTP OAuth or API key MCP settings

Configuration

Copy the
right shape.

Use the remote URL directly. Keep API keys out of shared configuration files and prefer OAuth when available.

Claude Code

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

JSON configuration

{
  "mcpServers": {
    "minds": {
      "url": "https://getminds.ai/mcp"
    }
  }
}

What the connection unlocks

From brief
to evidence.

Build grounded synthetic audiences, run durable panel studies, compare segments, and export structured findings. Explore Minds MCP →