·Minds Team

Integrations - Connect Minds Everywhere

Minds supports enterprise SAML SSO through Supabase Auth, delegated OneDrive file imports through Microsoft Graph, OAuth-secured MCP connections for AI assistants, and an embeddable website chat widget. This guide explains user setup, administrator responsibilities, permission boundaries, and the high-level data flow.

Connect Minds to AI assistants and your website. Use your Minds from ChatGPT, Claude, Cursor, Langdock, or any MCP-compatible client, or embed them directly on your site.

AI Assistants (MCP)

Use Minds directly from your AI assistant. Create Minds, run panel research, and analyze results — all through natural conversation.

MCP Server URL: https://getminds.ai/mcp

ChatGPT

  1. Go to ChatGPTSettingsConnected Apps
  2. Search for "Minds" or add the MCP URL: https://getminds.ai/mcp
  3. Click Connect and authorize via OAuth
  4. Start asking ChatGPT to create Minds and run panel research

ChatGPT renders interactive widgets inline — panel results with grouped responses, bar charts, and clickable Mind avatars.

Claude Desktop

Remote connector (recommended — enables interactive widgets):

  1. Open Claude Desktop → CustomizeConnectors
  2. Add https://getminds.ai/mcp
  3. Authorize via OAuth when prompted

Local connector (API key, text-only): Add to your config (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "mindsai": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://getminds.ai/mcp",
        "--header", "Authorization: Bearer minds_YOUR_API_KEY"]
    }
  }
}

Claude Code (CLI)

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

Cursor

  1. Open Cursor SettingsMCP
  2. Add server URL: https://getminds.ai/mcp
  3. Authorize when prompted

Widget support since Cursor v2.6.

Langdock

  1. Open LangdockIntegrationsAdd MCP Integration
  2. Enter URL: https://getminds.ai/mcp
  3. Select OAuth as authentication method
  4. Click "+ Add connection" and authorize
  5. Click "Test connection" to verify tools

All 15 tools available. Text responses with clickable links (no interactive widgets).

VS Code (GitHub Copilot)

  1. VS Code Settings → ExtensionsGitHub CopilotMCP Servers
  2. Add https://getminds.ai/mcp
  3. Authorize when prompted

Other MCP Clients

Any MCP-compatible client can connect to https://getminds.ai/mcp, including OpenRouter and Open WebUI. Clients that support OAuth will auto-discover the authorization flow. For clients without OAuth, use an API key (Settings → API Keys) as a Bearer token.

For the full tools reference and setup details, see the MCP documentation.


Chat Integrations

Slack

Coming soon - Chat with Minds in channels and DMs.

Microsoft Teams

Coming soon - Bring Minds to your Teams workspace.


Enterprise Single Sign-On (SAML)

Enterprise customers can sign in through a customer-managed identity provider such as Microsoft Entra ID or Okta. On the Minds Login or Register screen, choose email / SSO and enter your work email. Minds automatically recognizes registered SSO domains, removes the password fields, redirects to the configured identity provider, and returns through the existing PKCE callback at /auth/confirm.

Administrator setup

  1. Create a SAML 2.0 enterprise application in Microsoft Entra ID (or another identity provider). You can import the Minds metadata directly.
  2. If you enter the values manually, use:
    • Identifier / Entity ID: https://auth.getminds.ai/auth/v1/sso/saml/metadata
    • Reply URL / ACS: https://auth.getminds.ai/auth/v1/sso/saml/acs
    • Logout URL (optional): https://auth.getminds.ai/auth/v1/sso/saml/slo
  3. Send at least the email address and a stable user identifier as claims; display name is optional. Then assign the required users or groups to the application.
  4. Send Minds your identity provider's Federation Metadata URL or Federation Metadata XML, plus the verified sign-in domains. SAML does not require a client ID or client secret.
  5. Minds enables the connection, and both sides test identity-provider-initiated and Minds-initiated login with a test account.

MFA, device trust, sign-in risk, and location policies remain entirely in the customer's identity provider. Existing Minds accounts are reviewed before activation because SAML identities are not automatically merged with existing password, Google, Apple, or Microsoft logins.


Cloud Files & Designs (Google Drive, OneDrive & Figma)

Attach files straight from Google Drive or OneDrive in the chat input, when creating a group, and in a Mind's knowledge base. Google Drive uses the per-file drive.file scope. OneDrive uses delegated Files.Read and offline_access for the signed-in user's personal OneDrive. The Minds picker imports and stores only files the user explicitly selects. Minds does not crawl or synchronize the drive, and it cannot write, change, or delete OneDrive files.

The current OneDrive connector does not support shared folders outside the user's personal OneDrive or SharePoint and Teams document libraries. Those sources require a separate integration with broader Microsoft Graph permissions.

Setup: Click the Google Drive or OneDrive icon in the "+" attachment menu, or go to SettingsIntegrations. Authorize once, then pick files whenever you need them. The connection is remembered for next time.

Figma

Attach designs from Figma via the Figma icon in the "+" menu or SettingsIntegrations. A Figma file is a design rather than a document, so Minds renders the file (or the specific frame you link to) into an image and attaches that. After connecting, paste a link to a Figma file or frame and it attaches. Minds only receives the designs you paste, and only requests read access.

For organization admins

If your organization restricts third-party app access, an admin may need to approve Minds before your team can connect.

Google Workspace. In the Google Admin console, go to SecurityAccess and data controlAPI controlsApp access controlManage third-party app access. Add Minds by its OAuth client ID and set access to Trusted:

686849389800-f4ef6g5a2icmm7dhcdonuombqfncl2u8.apps.googleusercontent.com

Minds requests only the drive.file scope, which grants access to the individual files a user opens through the picker, not their entire Drive.

Microsoft 365 / Entra ID. An administrator can grant organization-wide consent by opening this link and signing in as an admin:

https://login.microsoftonline.com/common/adminconsent?client_id=fcf09c38-f994-4f8f-aab0-5eb8e6434271

Or, in the Microsoft Entra admin center: Enterprise applicationsMindsPermissionsGrant admin consent. Admin consent approves delegated Files.Read and offline_access for the organization; it does not grant Minds application-wide access to the organization's OneDrives. Each user then connects their own account under SettingsIntegrationsOneDrive and selects the files to import.


Enterprise Integration Architecture

Employees ── SAML ──> Customer identity provider ── assertion ──> Supabase Auth
    │                                                        │
    └──────────────────── Minds web app/API <── session ─────┘
                              │
                              ├── delegated Files.Read ──> Microsoft Graph
                              │          └── selected file import only
                              │
AI assistants ── OAuth 2.1/API key ──> Minds MCP server ──> authorized Minds APIs

The customer identity provider owns identities, MFA, Conditional Access, and user access policy. Supabase Auth validates the SAML assertion and creates the Minds session. Microsoft Graph is used only for a connected user's personal OneDrive and selected-file import. MCP clients use OAuth 2.1 with PKCE or a scoped Minds API key.

SSO, OneDrive, and MCP are separate trust relationships. Approving the OneDrive enterprise application does not enable SSO, and enabling SSO does not grant OneDrive or MCP access. Each integration has its own consent, token, and revocation path.


Embed Widget

Add a chat widget to your website for customer support, product demos, or interactive experiences.

Features:

  • Support-chat-style popup interface
  • Automatic light/dark theme detection
  • Mobile and desktop responsive
  • Session persistence across page loads

Setup:

  1. Go to SettingsIntegrationsEmbed Widget
  2. Select up to 3 Minds for your widget
  3. Copy the script tag and add it to your website

Basic usage:

<script
  src="https://getminds.ai/embed/chat-widget.js"
  data-widget-id="your-widget-id"
  async
></script>

Live Preview

Mocked — no server calls

Interactive embed widget — click the bubble to open, send a message, close and reopen to see localStorage persistence.

Configuration options:

AttributeDescriptionDefault
data-widget-idYour widget ID (required)-
data-languageForce language: en, de, es, fr, zh, tr, ar, ja, ko. Controls both the widget UI and the AI response language.Auto-detect
data-positionbottom-left or bottom-rightbottom-left
data-themelight or darkAuto-detect
data-max-messagesMax user messages before signup prompt (1–10)3
data-greeting-delayDelay in ms before initial greeting0
data-persist-sessionKeep conversation across pagestrue
data-sizeWidget size: standard or largestandard
data-primary-colorLauncher border / primary color as a hex value#000000
data-accent-colorLauncher chat-icon accent color as a hex value#00E14F
data-surface-colorLauncher surface color as a hex valuePage theme
data-launcher-labelText shown under the Mind name in the closed launcherChat with a Mind
data-z-indexCSS z-index for the widget999999

JavaScript API:

// Control the widget
ArtOfXChatWidget.open();
ArtOfXChatWidget.close();
ArtOfXChatWidget.toggle();

// Events
ArtOfXChatWidget.on('message', (data) => {
  console.log(data.role, data.content);
});

// Clear history
ArtOfXChatWidget.clearHistory();

Use ArtOfXChatWidget.open() from your own site button if you want a custom launcher.

ArtOfXWidget is kept as a back-compat alias for the same API.


Troubleshooting

MCP tools not showing up in your client Remove and re-add the connector, then complete the OAuth flow again. Some clients cache an empty tool list from a failed first connection.

"401 Unauthorized" with an API key Check that the key is sent as a Bearer token and starts with minds_ (Settings → API Keys).

Widget not appearing on your site Verify the data-widget-id matches the one in Settings → Integrations → Embed Widget, and that the script tag is not blocked by a consent manager.


Integrations bring Minds to where you already work. Set up once, use everywhere.