---
title: "Minds MCP Server for ChatGPT, Claude, and Cursor | Minds"
canonical_url: "https://getminds.ai/mcp/overview"
last_updated: "2026-10-01T13:17:26.057Z"
meta:
  description: "Connect the Minds MCP server to compatible AI clients and agents for Minds, Audiences, Studies, guided Studies, analytics, and export workflows."
  "og:description": "Connect the Minds MCP server to compatible AI clients and agents for Minds, Audiences, Studies, guided Studies, analytics, and export workflows."
  "og:title": "Minds MCP Server for ChatGPT, Claude, and Cursor | Minds"
  "twitter:description": "Connect the Minds MCP server to compatible AI clients and agents for Minds, Audiences, Studies, guided Studies, analytics, and export workflows."
  "twitter:title": "Minds MCP Server for ChatGPT, Claude, and Cursor | Minds"
---

Minds

Minds Team # **Minds MCP Server for ChatGPT, Claude, and Cursor** The Minds Model Context Protocol server connects compatible AI clients and agents to synthetic research workflows. It advertises a curated tool surface for interactive assistants and keeps further canonical tools callable across Minds, Audiences, Studies, Formations, knowledge, chat, analytics, and exports. The server currently advertises 27 tools and keeps 48 canonical tools callable, read from the live server. 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 integration with ChatGPT, Claude, Codex, Gemini CLI, Cursor, VS Code, 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](https://getminds.ai/mcp/setup). For every canonical tool and the live advertised surface, see the [Minds MCP tools reference](https://getminds.ai/mcp/tools). Agent authors should also read the [MCP operating guide for agents](https://getminds.ai/mcp/agents). ## Authentication The MCP server supports two authentication methods: - **OAuth 2.1** (recommended) — Clients like ChatGPT, Claude, Codex and Gemini CLI handle this automatically. You'll be prompted to log in to your Minds account when connecting. The [setup guide](https://getminds.ai/mcp/setup#scopes) lists the permissions a client requests. - **API Key** — For programmatic access, generate a key at Settings → API Keys (starts with `minds_`). Pass as `Authorization: Bearer minds_your_key`. ## Compatible Clients | Client | Widget | Auth | Setup |
| --- | :---: | :---: | --- | | **ChatGPT** | Client-dependent | OAuth | Web: **Plugins → Add → Create MCP App**, or Minds from the plugin directory; desktop app: **Plugins → Add → Add MCP server** (Streamable HTTP, then Save → Restart → Authenticate) | | **Claude (claude.ai and Claude Desktop)** | Client-dependent | OAuth | **Customize → Connectors → + → Add custom connector** | | **Claude Code** | No | OAuth or API key | `claude mcp add --transport http minds https://getminds.ai/mcp`, then `/mcp` → **Authenticate** | | **Codex** | No | OAuth or API key | `codex mcp add minds --url https://getminds.ai/mcp`, then `codex mcp login minds` | | **Gemini CLI** | No | OAuth | `httpUrl` entry in `~/.gemini/settings.json` | | **Cursor** | Client-dependent | OAuth | `url` entry in `~/.cursor/mcp.json` | | **VS Code (GitHub Copilot)** | Client-dependent | OAuth | **MCP: Add Server → HTTP**, then the server URL | | **Langdock** | No | OAuth | Integrations → Add MCP | | **Windsurf** | No | OAuth or API key | Cascade **… → Open MCP config file**, then a `serverUrl` entry | Every client sees the same advertised tools. Step-by-step instructions for each client are in the [setup guide](https://getminds.ai/mcp/setup); the [ChatGPT guide](https://getminds.ai/guide/integration-chatgpt) walks through every ChatGPT screen. All clients receive clickable links to open results in the Minds webapp, regardless of widget support. ## Advertised versus canonical tools`tools/list` returns 27 curated tools designed for ordinary interactive research. The server keeps 48 canonical tools callable in total, including lifecycle tools it does not advertise. 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](https://getminds.ai/mcp/tools). | Area | Tool | Description | Behavior |
| --- | --- | --- | --- | | Audiences | `list_audiences` | List Audiences. Lists the authenticated user's Audiences, most recently updated first, one page at a time (limit, default 20, and offset; nextOffset continues), with Mind counts, sharing state, and workspace or shared links. includeMinds adds each Audience's member Minds. searchQuery returns the best fuzzy name match instead of a page. Each Audience carries a workspaceUrl, the authenticated workspace link that stays valid verbatim, plus the top-level workspaceUrl for the Audience list; sharedAudienceUrl, when present, is the public share link for recipients. | Read-only | | `import_audience_sources` | Import Audience Research Sources. Imports supplied UTF-8 text, Markdown, CSV and JSON research files into account-owned storage. Accepts file contents rather than local paths. Identical file imports are safe to retry. Optional caller-reviewed grounding JSON binds distributions to existingFiles followed by files in sourceIdx order, returning a normalized snapshot and checksum for audience preview and creation. This operation creates no Audience or Minds and performs no web search or independent verification of supplied percentages. | Writes | | `create_audience_from_brief` | Create a Grounded Audience from a Brief. Creates an Audience from a free-text brief. The server researches the population, derives its defensible dimensions, and builds Minds with an explicit profile each and exact segment allocation. | Writes | | `get_audience_creation_progress` | Audience creation progress. Read one Audience creation operation and its members’ training progress. Never starts or retries creation. | Read-only | | `get_audience_limits` | Get Audience Limits. Returns the Audience size ceilings that apply to the authenticated account before an Audience is created: the per-Audience plan cap including any configured team allowance, the custom-size maximum, and the per-mode ceilings. Relevant whenever a size is named, "as many as possible" is asked for, or a creation mode is chosen. | Read-only | | `ask_audience` | Ask One Standalone Audience Question. Asks exactly one standalone question of one existing Audience. It creates a private Study for that Audience, starts asynchronous answers from its Minds, and returns the Study identifier and its links. | Writes | | `export_audience` | Export Audience Brief. Exports an Audience brief, or with kind "validation_report" the report of its validations (overall score calculation, every KPI, per-question answer shares, provenance), through the same renderer used by the web app. Brief: Markdown, PDF, DOCX, PPTX. Validation report: Markdown, PDF, DOCX, XLSX. Binary artifacts are returned as base64. | Writes | | `duplicate_audience` | Duplicate Audience. Copy an Audience with independent copies of its Minds and all they know. | Writes | | Studies | `list_studies` | List Studies. Lists the authenticated user's Studies, most recently updated first, one page at a time: limit (default 20) and offset, with nextOffset to continue. Each row carries the Study's Audiences with their Mind counts, stored message count, sharing state and links. searchQuery returns the best fuzzy name match instead of a page. | Read-only | | `create_study` | Create a Study. Creates a Study workspace from existing Audiences or inline Audience configurations. It does not ask questions or run research, and follow-up research inside an existing Study needs no new Study. | Writes | | `ask_study` | Ask One Standalone Question in a Study. Submits exactly one respondent-visible question in an existing Study: one standalone question, or one adaptive follow-up whose wording could not be known before earlier results. | Writes | | `get_study_status` | Get Study Status. Returns and shows a Study's current state: progress for in-flight questions, completed per-Audience results, the linked Minds, Study links, and the status of a requested async export job. Values can be numeric answers or classified summary labels, and message fields carry the original Mind responses where available. locale is the Study's display locale, not a guarantee of the language of every answer. | Read-only | | `export_study` | Export Study Results. Starts an asynchronous export of Study results and returns an export job ID. Supports executive briefs and full reports in PDF, DOCX, PPTX, or Markdown, plus raw data in CSV, XLS, or SPSS SAV. | Writes | | `duplicate_study` | Duplicate Study. Copy a Study with all its questions and results over the same Audiences. | Writes | | `export_heatmap` | Export Website Heatmap. Exports a completed website heatmap from a Study result, identified by the message ID reported with the completed result. Returns the same ZIP archive as the web app, including its unified-renderer PDF report, Markdown, images, and metadata. | Writes | | `run_study_heatmap` | Run Study Asset Heatmap. Read or start a question asset heatmap, with the same behavior as Minds UI. For a specific video or image pass assetKey: its saved upload path (chat/...) or normalized URL. Only assets assigned to that question can be analyzed. GET returns assetHeatmaps keyed by asset identity; start with assetKey reuses completed analysis for that asset, while start without assetKey can rerun analysis. Website analysis visits the assigned public URL. Starting analysis uses one response per Mind and requires Premium. Selecting a different video does not change the question results. | Writes | | `get_study_summary` | Get Study Summary. Returns or refreshes the semantic summary for a Study as Markdown plus flexible evidence blocks. Website, image, and video analyses retain heatmap-compatible block metadata. | Writes | | Research planning | `plan_study_questions` | Plan a Multi-Question Block in a Study. Creates or revises a non-executing draft for a multi-question plan inside an existing Study. Saving never starts research. To change a draft, pass `draft.id` with its current `draft.revision` — re-sending a reworded `request` creates a SECOND draft instead of revising; a stale revision is rejected. | Destructive | | `run_study_questions` | Run a Confirmed Multi-Question Block. Executes one stored draft revision inside its Study, after the person has explicitly confirmed that exact revision. One execution submits the whole draft — every named module and every question — as a single durable run; there is no per-question or per-module execution. | Writes | | `list_research_methods` | List Research Methods. Lists Minds research methods with availability, complexity, executable status, and fallback metadata. Results distinguish currently executable methods from experimental or planned methods. | Read-only | | Templates & drafts | `list_study_drafts` | List Study Drafts. Lists durable unfinished study drafts, or returns the complete saved planning state for one exact draft ID. Draft records are distinct from running or completed studies. | Read-only | | `list_study_templates` | List Study Templates. Lists your own and team-shared Study templates, most used first, or returns one exact template including its revision, research method, questions, response settings and question attachments. configuration.methodId names the registered research method the Study runs under, and configuration.questions is a fixed, pre-registered instrument ready to be transcribed into a question plan. | Read-only | | `save_study_draft` | Save Study Draft. Creates or checkpoints an unfinished Quick or Custom Study draft without starting research. It saves the objective, context, selected Audiences, method, questions, sources, and current planner step. Revisions replace the saved planning state and require the exact draft ID and expected revision; stale writes are rejected. For a retryable creation, choose idempotencyKey before the first save and reuse it after an uncertain result. | Destructive | | `manage_study_template` | Manage Study Template. Saves, explicitly updates or uses a Custom research template. Deleting one is a separate operation. | Destructive | | `delete_study_template` | Delete Study Template. Permanently deletes one saved Study template owned by the authenticated user. The template and its stored configuration are gone; Studies and drafts already created from it are unaffected. Teammates with shared access cannot delete a template they do not own. | Destructive | | Minds | `export_mind` | Export Mind Persona Profile. Generates a branded profile for one existing Mind, identified by exact ID or the best fuzzy name match among the newest 1,000 Minds. Markdown is returned inline by default; PDF, DOCX, and PPTX artifacts are returned as base64 with a workspace link. | Writes | | `get_shared_mind_knowledge` | Read Shared Mind Sources. Read shared Mind sources and assessments. | Read-only | ## Interactive Preview Minds currently registers three MCP views: Study results (for a new question and for an existing Study), research-plan review, and Audience creation. They reuse Minds UI components. The client determines the surrounding frame and available interactions. 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. Each tab is one view, with the tools that open it; loading and in-progress examples are fixed snapshots, not live research. 3 widgets · 13 preview states ### **Inspect every MCP widget**Shown by:`ask_audience``ask_study``get_study_status`