MCP-Integration

Der Server bietet derzeit 40 Tools an und hält 70 kanonische Tools aufrufbar; beide Werte werden live vom Server gelesen. Maßgeblich ist die Antwort des verbundenen Servers auf tools/list.

Minds stellt einen MCP-Server (Model Context Protocol) bereit, über den KI-Assistenten synthetische Research-Studies erstellen, Multi-Perspektiven-Umfragen durchführen und direkt mit KI-Minds interagieren können. Damit lässt sich Minds in ChatGPT, Claude, Codex, Gemini CLI, Cursor, VS Code und andere MCP-kompatible Clients einbinden.

Was ist MCP?

Das Model Context Protocol (MCP) ist ein offener Standard, mit dem KI-Assistenten sicher auf externe Tools und Datenquellen zugreifen können. Mit unserer MCP-Integration kannst du:

KI-Minds erstellen und verwalten (Expert:innen, Personas, digitale Zwillinge)
Research-Studies mit Audiences von Fachexpert:innen aufbauen
Umfragen an mehreren Perspektiven parallel laufen lassen
Statistische Auswertungen der Study-Antworten abrufen
Gebrandete PDF-Reports, Markdown-Zusammenfassungen oder Rohdaten exportieren
Minds in wiederverwendbare Audiences organisieren

MCP-Server-URL

https://getminds.ai/mcp

Für die Einrichtung nach Client siehe den Minds MCP Setup Guide. Alle kanonischen Tools und die live angebotene Tool-Auswahl stehen in der Minds MCP Tool-Referenz. Wer Agents entwickelt, sollte außerdem den MCP-Leitfaden für Agents lesen.

Authentifizierung

Der MCP-Server unterstützt zwei Authentifizierungsmethoden:

OAuth 2.1 (empfohlen) — Clients wie ChatGPT, Claude, Codex und Gemini CLI übernehmen das automatisch. Beim Verbinden meldest du dich in deinem Minds-Konto an. Welche Berechtigungen ein Client anfordert, steht im Setup Guide.
API Key — Für programmatischen Zugriff: einen Key unter Settings → API Keys erzeugen (beginnt mit minds_). Als Authorization: Bearer minds_your_key mitsenden.

Kompatible Clients

Client	Widget	Auth	Einrichtung
ChatGPT	Clientabhängig	OAuth	Web: Plugins → Add → Create MCP App oder Minds aus dem Plugin-Verzeichnis; Desktop-App: Plugins → Add → Add MCP server (Streamable HTTP, dann Save → Restart → Authenticate)
Claude (claude.ai und Claude Desktop)	Clientabhängig	OAuth	Customize → Connectors → + → Add custom connector
Claude Code	nein	OAuth oder API key	`claude mcp add --transport http minds https://getminds.ai/mcp`, dann `/mcp` → Authenticate
Codex	nein	OAuth oder API key	`codex mcp add minds --url https://getminds.ai/mcp`, dann `codex mcp login minds`
Gemini CLI	nein	OAuth	`httpUrl`-Eintrag in `~/.gemini/settings.json`
Cursor	Clientabhängig	OAuth	`url`-Eintrag in `~/.cursor/mcp.json`
VS Code (GitHub Copilot)	Clientabhängig	OAuth	MCP: Add Server → HTTP, dann die Server-URL
Langdock	nein	OAuth	Integrations → Add MCP
Windsurf	nein	OAuth oder API key	In Cascade … → Open MCP config file, dann ein `serverUrl`-Eintrag

Alle Clients sehen dieselben angebotenen Tools. Schritt-für-Schritt-Anleitungen für jeden Client stehen im Setup Guide; der ChatGPT-Leitfaden führt durch jeden ChatGPT-Bildschirm.

Alle Clients erhalten anklickbare Links, um Ergebnisse in der Minds-Web-App zu öffnen — unabhängig davon, ob Widgets unterstützt werden.

Angebotene und kanonische Tools

tools/list liefert 40 kuratierte Tools für die gewöhnliche interaktive Forschung. Insgesamt hält der Server 70 kanonische Tools aufrufbar, darunter Lebenszyklus-Tools, die er nicht anbietet. Explizite Integrationen können diese Tools über ihren kanonischen Namen aufrufen, sofern der Client konfigurierte oder direkte Tool-Aufrufe unterstützt. Diese Trennung hält die Standard-Tool-Auswahl für das Modell fokussiert und bewahrt zugleich den vollständigen unterstützten Funktionsumfang.

Tool-Aliasse können aus Kompatibilitätsgründen aufrufbar bleiben, Agents sollten aber immer die kanonischen Namen aus der Tool-Referenz verwenden.

Bereich	Tool	Beschreibung	Verhalten
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 links. includeMinds adds each Audience's member Minds. searchQuery filters by name (case-insensitive, all matches, paged). Each Audience's workspaceUrl is the authenticated workspace link, valid verbatim; sharedAudienceUrl, when present, is the public share link for recipients. addOnRequired marks a paid Marketplace Audience the user has not subscribed to: prefer the user's own Audiences, and only use it after the user subscribes.	Nur lesend
	`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.	Schreibend
	`create_audience_from_brief`	Create a Grounded Audience from a Brief. Researches a free-text population brief and builds a new Audience of Minds with explicit profiles and exact segment allocation. A new brief returns an evidence-backed draft for review; draft.rework or the displayed review revises that draft before confirmation, and creation requires the user-accepted draft or quota snapshot and its checksum. Every new brief starts a separate draft and, once confirmed, a separate Audience. An Audience that already exists is changed in place by recalibrating it by its id, never rebuilt from a new brief. Supports reviewed respondent datasets. Creation is asynchronous and returns an operation ID. Audiences are private unless link sharing is enabled.	Schreibend
	`get_audience_creation_progress`	Audience creation progress. Reads progress and never starts or retries anything: an Audience creation by operationId, with its members’ training; or an existing Audience by audienceId, with its member training and background research, or with recalibrationId one recalibration’s status, retained result or terminal error.	Nur lesend
	`render_audience_review`	Show Audience Creation. Shows source research, distributions, proposed Minds, the draft and training for one or more Audience operations, display only: the user confirms or asks for changes in chat. Multiple operations appear in independent tabs within one widget.	Nur lesend
	`get_audience_limits`	Get Audience Limits. Returns the Audience size ceilings for the authenticated account before an Audience is created: the per-Audience plan cap (including any 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.	Nur lesend
	`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.	Schreibend
	`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.	Schreibend
	`duplicate_audience`	Duplicate Audience. Copy an Audience with independent copies of its Minds and all they know.	Schreibend
	`recalibrate_audience`	Change an Existing Audience. Changes an existing Audience in place: it keeps its id, its Minds keep theirs (except copies below), and no Mind is deleted. Covers composition and trait edits, a population pivot, adding members, an exact chart selection (`distributions`), new sources and going deeper (`deepen`), and re-runs its research grounding. Owner, or verified Minds staff with existing direct Audience admin collaboration or an active owner-issued support grant. Staff support is limited to composition amendments: no growth, new sources, Go deeper or shared-Mind waiver. Asynchronous: the result is an accepted operation with its id, not a completed change. Queues behind another edit of the Audience and waits for a Study run on its members. Members shared with other Audiences are replaced here by copies with new ids. Reusing requestKey with identical input retries safely.	Destruktiv
	`manage_audience_support`	Manage Audience Support Access. Manage owner-issued, expiring staff access to one Audience’s composition and receipts. Staff cannot self-grant. Revocation stops new work at checkpoints; completed changes remain. No membership, growth, deletion or billing changes.	Destruktiv
	`attach_study_audiences`	Attach Audiences to Study. Adds existing accessible Audiences without removing others, planning or starting research. Returns attached and alreadyAttached IDs; retries are safe. With link sharing on, the Audiences and their Minds become publicly readable. Access and plan eligibility are validated first.	Schreibend
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 filters by name (case-insensitive, all matches, paged). Minds and per-question results come from the Study status.	Nur lesend
	`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.	Schreibend
	`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.	Schreibend
	`get_study_status`	Get Study Status. Returns Study progress, per-Audience results, original Mind responses, links and export status. In-flight questions report zero Minds answered until completion; partial per-Mind progress is not persisted. questionId selects one question; runId selects a confirmed run with question-level counters. Without either, results cover the entire Study. Values and labels are written in the Study display locale, returned as locale: the language of its confirmed plan, else the stored Study locale, else English.	Nur lesend
	`render_study_results`	Show Final Study Results. Shows the results of finished questions (summary, key findings, Audience breakdowns, Mind responses): one question, or a run's finished questions while the rest still run. Use it whenever the user asks about results. Requires exactly one of questionId or runId.	Nur lesend
	`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.	Schreibend
	`duplicate_study`	Duplicate Study. Copy a Study with all its questions and results over the same Audiences.	Schreibend
	`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.	Schreibend
	`get_study_heatmap`	Read Study Asset Heatmap. Reads saved heatmaps of an assigned question asset. Optional assetKey selects its saved upload path or normalized URL. Returns assetHeatmaps without starting analysis, spending responses or visiting websites.	Nur lesend
	`start_study_heatmap`	Start Study Asset Heatmap. Starts attention analysis of an assigned image, video or website. Uses one response per Mind and needs a paid plan. assetKey reuses completed analysis of that asset; omitting it may replace earlier derived results. Websites are visited publicly. Explicit approval is required; question answers are preserved.	Destruktiv
	`create_study_plan`	Create Study Plan. Creates a non-executing draft in an existing Study with its Audiences already attached. The setup operation for two or more known questions: every question known now belongs in this one draft, in cohesive named modules. A one-question draft is only for genuinely standalone research or an adaptive follow-up. request designs questions; questions preserves a fixed instrument verbatim. Each Mind sees only its own earlier answers; askIf applies respondent-level skip logic. With multiple attachments, stimulus.questionAttachments assigns each question; [] means none. Saving bounded history may prune older revisions. Research has not started; the returned draft revision needs review and later explicit confirmation.	Destruktiv
	`revise_study_plan`	Revise Study Plan. Revises one saved draft at its current draft.id and draft.revision without starting research. Accepts edits, refinement, clarification answers or response-format corrections. Stale revisions fail. Fixed questions stay verbatim when only clarification answers change. Bounded history may prune older revisions; the changed draft requires review again.	Destruktiv
	`get_study_plan`	Read Study Plan. Reads the latest saved revision and full review of one draft. Creates or changes nothing and starts no research.	Nur lesend
	`render_study_plan`	Show Study Plan. Shows a saved Study draft at its current revision for interactive review and confirmation. Research has not started.	Nur lesend
	`read_study_summary`	Read Study Summary. Reads saved whole-Study Markdown, evidence blocks and metadata. Does not regenerate or replace the summary.	Nur lesend
	`refresh_study_summary`	Refresh Study Summary. Generates and saves a whole-Study summary after explicit approval. Replaces the prior summary without restore history; answers and questions are preserved. force regenerates unchanged coverage. Returns Markdown and evidence blocks.	Destruktiv
Forschungsplanung	`start_study_run`	Start Confirmed Study Run. Runs one reviewed draft revision after explicit confirmation in a later user turn; skipping review is not confirmation. One execution submits the whole draft as a single durable run. It is refused as a whole before using Minds or quota if the revision, capabilities, method or source-readability checks fail. Advanced methods need explicit opt-in. Each Mind answers in order seeing its own earlier answers; askIf gates items. Contradictions are flagged, never rewritten.	Schreibend
	`resume_study_run`	Resume Study Run. Resumes an existing plan-limited Study run in place after explicit user approval and the required paid-plan entitlement. Keeps the originally confirmed questions and response contracts and does not ask questions already answered. Does not start a new draft or change the run design.	Schreibend
	`list_research_methods`	List Research Methods. Reads the fixed Minds research-method catalog in one operation, including availability, complexity and fallback method. includePlanned only filters the returned catalog. It does not create, configure or execute a method, and the catalog cannot be edited through this tool.	Nur lesend
Vorlagen & Entwürfe	`list_study_drafts`	List Study Drafts. Lists a page of unfinished Study draft summaries, newest first, or returns the complete saved planning state for one exact draft ID. Draft records are distinct from running or completed studies.	Nur lesend
	`list_study_templates`	List Study Templates. Lists your own and team-shared Study templates, most used first, as a page of summaries (templateId, name, revision, method, question count), or returns one exact templateId with its revision, research method, questions, response settings and question attachments. configuration.questions is a fixed, pre-registered instrument and configuration.methodId the research method it runs with; both can be planned as they are.	Nur lesend
	`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 change only the fields given 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.	Destruktiv
	`save_study_template`	Save Study Template. Creates a private Custom template with its questions, response settings, attachments and method. template.requestId enables safe retries. Does not change existing templates, create a draft or start research.	Schreibend
	`update_study_template`	Update Study Template. Updates one owned Custom template at update.expectedRevision. Replaces supplied fields without restore history and may share it with the team. Requires explicit approval; stale revisions fail. Does not start research.	Destruktiv
	`use_study_template`	Create Draft From Study Template. Creates an independent editable Study draft from a readable template at use.expectedRevision. Reuse use.requestId for retries of the same intended draft. Fresh context and Audiences are added in the web app; the template is unchanged and research does not start.	Schreibend
	`delete_study_template`	Delete Study Template. Only for saved Study templates; it cannot delete Studies, Audiences, Minds or answers. Permanently deletes one template owned by the authenticated user. Studies and drafts already created from it are unaffected. Teammates with shared access cannot delete a template they do not own.	Destruktiv
Minds	`export_mind`	Export Mind Persona Profile. Generates a branded profile for one existing Mind, identified by exact ID or name (partial names and typos resolve to the closest). Markdown is returned inline by default; PDF, DOCX, and PPTX artifacts are returned as base64 with a workspace link.	Schreibend
Minds	`get_shared_mind_knowledge`	Read Shared Mind Sources. Read shared Mind sources and assessments.	Nur lesend

Interaktive Vorschau

Minds registriert derzeit drei MCP-Ansichten: Study-Ergebnisse (für eine neue Frage und für eine bestehende Study), Forschungsplan-Prüfung und Audience-Erstellung. Sie verwenden Minds-UI-Komponenten. Rahmen und Interaktionen hängen vom Client ab.

Die aktuelle Planansicht zeigt den gespeicherten Entwurf zur Prüfung. Bitte im Gespräch um Änderungen und bestätige die neueste Revision ausdrücklich, bevor der Assistent sie ausführt. Das Anzeigen eines Plans startet keine Study.

Erkennt ein Widget einen mobilen Host, zeigt es einen Link zum Fortsetzen in Minds. Interaktive Bedienelemente und Widget-Polling starten dort nicht. Das betrifft die Darstellung, nicht die Verfügbarkeit der MCP-Tools. Einschränkungen des Clients gelten weiterhin.

Die folgenden Beispiele verwenden illustrative Daten. Jeder Tab zeigt eine Ansicht mit den Tools, die sie öffnen; Lade- und Fortschrittsbeispiele sind feste Momentaufnahmen, keine laufende Forschung.

3 Widgets · 13 Vorschauzustände

Alle MCP-Widgets ansehen

The first render, before the host delivers the question's data.

Beispieldaten · Darstellung variiert je nach Client

n8n-Workflows

Verwenden Sie den Minds-Community-Node für n8n, um Studies zu erstellen, Forschungspläne in der Vorschau anzuzeigen, Studies und gespeicherte Zusammenfassungen abzurufen oder eine Operation für einen AI Agent bereitzustellen. Installieren Sie n8n-nodes-minds auf selbst gehostetem n8n und verbinden Sie einen Minds API-Schlüssel. Das Paket ist auf npm veröffentlicht; die n8n-Verifizierung wird geprüft, daher ist es auf n8n Cloud noch nicht verfügbar. Überprüfen und starten Sie die Forschung separat in Minds.