Skip to content
Dark mode

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.

Some Mindtickle tools open an interactive screen, called an MCP app, inside the AI client (for example, an AI Tutor tutorial). Whether the screen appears depends on whether your AI client supports MCP apps. See MCP apps.

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.

Add Mindtickle as a custom MCP app under Workspace settings > Apps (Business, Enterprise, and Edu plans, with limited access also available on Pro plans through developer mode). See OpenAI’s developer mode and MCP apps documentation.

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 (via Gemini Enterprise Agent Platform)

Section titled “Gemini (via Gemini Enterprise Agent Platform)”

Google’s path for connecting Mindtickle to Gemini-powered experiences runs through the Gemini Enterprise Agent Platform: an admin configures Mindtickle as an MCP tool on an agent there, then surfaces the agent through Gemini or an embedded experience. See Google’s documentation on connecting MCP servers in Gemini Enterprise.

Add Mindtickle as a custom MCP connector at grok.com/connectors by choosing New Connector > Custom, then entering the MCP server URL. On Grok Business and Enterprise, a team admin must first provision the connector in the cloud console before members can use it. See xAI’s documentation on connectors.

Add Mindtickle as an MCP server in Cursor’s settings or mcp.json. See Cursor’s MCP documentation.

Add Mindtickle as an MCP server in Windsurf’s Cascade settings. See Windsurf’s Cascade MCP integration documentation.

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.

Add Mindtickle as an MCP server in Continue’s configuration. See Continue’s MCP documentation.

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 Authorization header (for programmatic integrations).
  • Tools exposed: See Supported tools for the full list.
  • Scope-control modes: User-controlled (default) or admin-controlled (with client_id and client_secret issued 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.