Minds MCP Server for ChatGPT, Claude, and Cursor

Tool availability depends on deployment configuration: ordinary discovery exposes 23 tools, or 24 when list_model_connections is enabled, with 42 or 43 canonical tools registered respectively. Treat the connected server’s tools/list response as authoritative.

Minds provides a Model Context Protocol (MCP) server that lets AI assistants create reusable Audiences, run cohesive multi-question Studies, and interact with individual Minds. This enables seamless integration with tools like ChatGPT, Claude Desktop, Cursor, and other MCP-compatible clients.

What is MCP?

The Model Context Protocol (MCP) is an open standard that enables AI assistants to securely connect to external tools and data sources. With our MCP integration, you can:

• Create and manage AI Minds (experts, personas, digital twins)
• Build Studies with reusable Audiences of domain experts or consumers
• Run survey-style questions across multiple perspectives
• Get statistical analytics on Study responses
• Export branded PDF reports, markdown summaries, or raw data
• Organize Minds into reusable Audiences
• Create grounded audiences from briefs or respondent datasets
• Plan, explicitly confirm, run, and resume durable research Studies
• Manage knowledge, Formations, lifecycle actions, and stateful chats

MCP Server URL

https://getminds.ai/mcp

For setup instructions by client, see the Minds MCP setup guide. For all 42–43 canonical tools and the 23–24-tool advertised surface, see the Minds MCP tools reference. Agent authors should also read the MCP operating guide for agents.

Authentication

The MCP server supports two authentication methods:

• OAuth 2.1 (recommended) — Clients like ChatGPT and Claude Desktop handle this automatically. You'll be prompted to log in to your Minds account when connecting.
• API Key — For programmatic access, generate a key at Settings → API Keys (starts with minds_). Pass as Authorization: Bearer minds_your_key.

Compatible Clients

All clients receive clickable links to open results in the Minds webapp, regardless of widget support.

Advertised versus canonical tools

tools/list returns 23–24 curated tools designed for ordinary interactive research. The server also keeps 19 additional canonical lifecycle and compatibility tools registered, for 42–43 canonical tools in total. Explicit integrations can call those tools by canonical name when the client supports configured or direct tool calls. This split keeps the default model surface focused while preserving the full supported capability contract.

Tool aliases may remain callable for compatibility, but agents should always use canonical names from the tools reference.

Interactive Preview

Minds currently registers three MCP views: creation progress, Study results and conversations, and research-plan review. They reuse Minds UI components. The client determines the surrounding frame and available interactions. The information preview below is illustrative; lookup tools return structured/text results without opening that view.

The current plan view displays the saved draft for review. Request changes in the conversation, then explicitly confirm the latest revision before the assistant runs it. Viewing a plan does not start a Study.

When a widget detects a mobile host, it displays a link to continue in Minds; interactive controls and widget polling do not start. This changes the widget presentation, not the MCP server's tool availability. Client restrictions still apply.

The examples below use illustrative data. Switch tabs to inspect creation, information, and response states; loading examples are fixed snapshots, not live research.

n8n workflows

Building an n8n automation instead of an MCP client? The Minds n8n integration connects directly to the Study API and can serve as an AI Agent tool. The npm package supports self-hosted n8n while n8n verification remains under review.