AI clients
Find vendor setup documentation for connecting supported AI clients to the Mindtickle MCP server.
Choose an AI client that supports remote MCP connections over HTTP and Mindtickle’s authentication flow. The links below lead to vendor setup instructions. Features, plan requirements, and settings vary by client; organization-managed connections may require an administrator. Clients may call the connection a connector, app, tool, or MCP server.
You need your Mindtickle MCP server URL. For managed connectors, see Set up the connector for the URL and scope-control modes, then Connect your account to authorize access. For a programmatic integration, follow Build a custom client.
Hosted AI assistants
Section titled “Hosted AI assistants”Claude (Team and Enterprise)
Section titled “Claude (Team and Enterprise)”An organization Owner or Primary Owner adds the connector under Organization settings > Connectors. Members then authorize their own accounts under Customize > Connectors. See Anthropic’s documentation on custom connectors using remote MCP.
ChatGPT
Section titled “ChatGPT”Follow OpenAI’s MCP connection instructions to enable developer mode, add the Mindtickle server URL, and review the discovered tools. Availability depends on your account and workspace policy. Follow your organization’s approval process before making the connection available to members.
Microsoft 365 Copilot (via Copilot Studio)
Section titled “Microsoft 365 Copilot (via Copilot Studio)”Microsoft 365 Copilot doesn’t add MCP connectors directly. Instead, an admin or agent maker adds Mindtickle as an MCP tool on an agent inside Microsoft Copilot Studio, then publishes that agent to Microsoft 365 Copilot. See Microsoft’s documentation on connecting agents to an existing MCP server.
Gemini Enterprise
Section titled “Gemini Enterprise”Configure Mindtickle as an MCP tool for a Gemini Enterprise agent workflow. See Google’s Connect MCP servers instructions.
Coding assistants
Section titled “Coding assistants”Cursor
Section titled “Cursor”Add Mindtickle as an MCP server in Cursor’s settings or mcp.json. See Cursor’s MCP documentation.
Windsurf
Section titled “Windsurf”Add Mindtickle as an MCP server in Windsurf’s Cascade settings. See Windsurf’s Cascade MCP integration documentation.
VS Code
Section titled “VS Code”Add Mindtickle as an MCP server in VS Code’s agent/MCP settings. See Visual Studio Code’s MCP servers documentation.
Add Mindtickle as an MCP server in Cline’s MCP settings. See Cline’s MCP documentation.
Continue
Section titled “Continue”Add Mindtickle as an MCP server in Continue’s configuration. See Continue’s MCP documentation.
Other MCP-compatible clients
Section titled “Other MCP-compatible clients”For other clients, verify support for remote MCP connections over HTTP and the authentication flow you intend to use:
- Connector URL:
https://{mindtickle-instance-url}/mcp - Authentication: OAuth 2.0 with consent (handled by the client application) or Bearer JWT in the
Authorizationheader (for programmatic integrations). - Tools exposed: See Supported tools for the full list.
- Scope-control modes: User-controlled (default) or admin-controlled (with
client_idandclient_secretissued by your Mindtickle Customer Success Manager (CSM)).
Follow your client’s documentation to configure the connection. For client credentials authentication, exchange client_id and client_secret for an access token; do not send those credentials directly to the MCP endpoint. See Build a custom client.