Mindtickle MCP

Connect AI clients to Mindtickle with the Model Context Protocol, choose a connection path, and understand access requirements.

View as Markdown

The Mindtickle MCP server is Mindtickle’s implementation of the Model Context Protocol (MCP), an open standard that lets AI clients connect to external tools, data sources, and services. It exposes Mindtickle capabilities as tools that MCP-compatible AI clients can call during user conversations, without a separate point-to-point integration for each compatible client.

With the Mindtickle MCP server, your sales reps can ask questions in their AI client (such as “Find the latest battle card for our top competitor” or “Summarize my last call with Example Organization”) and receive answers drawn from their Mindtickle content, without leaving the tool they are already working in.

Who this is for

Choose a guide based on your role.

Role	What they do	Articles
IT admin	Manages which third-party apps and connectors your organization can use inside AI clients such as Claude or ChatGPT. This role requires admin access in the AI client, not the Mindtickle admin site.	Set up the connector
Developer	Builds or integrates a custom AI client or agent directly against the Mindtickle MCP server’s API.	Supported tools, then Build a custom client
Sales rep	Uses Mindtickle content and tools day-to-day through an AI client.	Connect your account to get set up, then Use cases for what’s possible once connected

What you can do

Connect an MCP-compatible AI client to search Mindtickle content, ask Seller Copilot questions, look up CRM records, create or manage Digital Sales Rooms, read Deal Guides and recorded calls, check your own training progress, see how your team is doing with Manager Insights, and open AI Tutor tutorials (beta). Most tools require a scope, and results respect the user’s existing Mindtickle permissions. See Supported tools for the available tools, their requirements, and their effects.

Available tools

The Mindtickle MCP server exposes the following tools, grouped into read-only tools and write tools. Only the tools matching a user’s granted scopes are available to call. For each tool’s parameters, response, and detailed behavior, see Supported tools.

Read-only tools

mindtickle_search: Searches across Mindtickle learning content (assets, modules, files, series, asset hubs, tags, and peers) using hybrid keyword and AI-powered semantic search.
mindtickle_seller_copilot_ask: Sends a conversation to Mindtickle’s Seller Copilot and generates the assistant’s response, drawing on modules, assets, and Call AI recordings.
find_deals: Looks up deals (CRM opportunities) by name, company, or stage.
find_companies: Looks up companies (CRM accounts) by name.
find_contacts: Looks up buyer and prospect contacts by name, email, or associated company.
find_rooms: Finds existing Digital Sales Rooms by name, or by the deal, company, or contact linked to them.
fetch_room: Retrieves the full details of a single Digital Sales Room by its ID.
fetch_deal_guide: Returns the pre-generated Deal Guide for one deal, including pains, objections, the buying committee, competitor intel, and recommended next steps.
find_call: Searches the user’s recorded sales calls and meetings by participant, account or opportunity, time window, or topic.
fetch_call: Retrieves detailed information for one or more recorded calls, including the transcript, key moments, action items, or summary.
fetch_learner_insights: Returns your own training progress: overall progress, assigned series and modules, completed modules, certificates, and badges.
fetch_manager_team_insights: Returns Manager Insights: how your direct reports are doing on readiness, training, coaching, and conversations, with drill-downs into a series, module, learner, or training category. Requires the manager role in Mindtickle.
find_tutorial (beta): Lists your AI Tutor tutorials, with your progress in each.
fetch_tutorial (beta): Opens an AI Tutor tutorial in an interactive screen inside your AI client.

Write tools

create_room: Creates a new Digital Sales Room and returns its identifiers and links.
edit_room: Updates an existing Digital Sales Room, including its guest list, access controls, and content.
share_room: Emails an existing Digital Sales Room’s link to one or more buyers, inviting them to open it.
create_contacts: Turns one or more email addresses into contacts you can add to a Digital Sales Room’s guest list.

MCP apps

Some tools open an interactive screen inside your AI client instead of returning text. These screens are called MCP apps. The Mindtickle MCP server controls what each screen shows. Your AI client displays the screen, but it can’t see what happens inside it.

For example, fetch_tutorial opens the AI Tutor screen for one tutorial.

Tutorial cards show in AI clients that support MCP apps, such as Claude, ChatGPT, VS Code, Cursor, and Goose. Other AI clients, including Copilot Studio, do not offer fetch_tutorial. They can still list tutorials with find_tutorial, which returns a link to each one. For what each tool does, see Supported tools.

Connection options

Both connection options use the same Mindtickle MCP server. Available tools depend on the granted scopes, and results respect the user’s Mindtickle permissions. Choose the option that matches how your AI client authenticates.

Setup detail	Programmatic integration	Custom connector in an MCP client app
Who it’s for	Developers and integrators building or configuring an AI client, agent, or automation.	Organization admins and end users of a managed, MCP-compatible AI client application (for example, Claude for Teams or Claude Enterprise).
How setup works	Manual configuration in code or a config file (for example, editing Cursor’s `mcp.json`).	Point-and-click setup through the client application’s admin UI. Each rep then authorizes their own access through an OAuth consent screen.
Authentication flow	OAuth 2.0 client credentials grant. The integrator obtains a `client_id` and `client_secret` from Mindtickle, exchanges them for a short-lived JWT, and sets the token in the `Authorization` header.	OAuth 2.0 authorization code with consent. Users are redirected to a Mindtickle consent screen, click to authorize, and the client application handles the token internally.
Token management	The integrator caches the token, checks `expires_in`, and obtains a replacement before it expires.	The AI client manages tokens. Reconnection depends on access revocation, refresh-token expiry, and whether the client registered for a refresh token.
Setup guide	Build a custom client	Set up the connector (admin), then Connect your account (rep)

Authentication and access control

All requests to the Mindtickle MCP server are authenticated using OAuth 2.0 and short-lived Bearer tokens (JWTs). On every request, the server validates the token and checks the scopes it carries before invoking any tool. This ensures that:

Only authorized clients can connect.
Each tool call runs in the context of an identified Mindtickle user.
Results respect the same permissions and content access policies that apply to that user inside Mindtickle.
Only the tools matching the granted scopes are exposed and callable.

For detailed information on tools, see Supported tools. For scopes, grant types, the token endpoint, and error codes specific to your connection path, see Build a custom client or Set up the connector.

Availability and access

Credentials and enablement: The integration is not self-service. Mindtickle must enable it on your instance, and any client_id and client_secret required for the programmatic integration path or for admin-controlled connector setup are issued only by the Mindtickle team.
How to get started: Contact your Customer Success Manager or account team to enable the integration and request credentials.

In this section

Set up the connector: Configure the connector and scope controls for your organization.
Connect your account: Authorize your account, use the connector, and troubleshoot access.
AI clients: Find setup guidance for your AI client.
Build a custom client: Obtain credentials, authenticate, and call tools from your integration.
Supported tools: Review tool parameters, response fields, limits, and side effects.
Use cases: Explore prompts and workflows for content, Digital Sales Rooms, deals, calls, training, and Manager Insights.
Best practices: Apply security, reliability, and integration guidance.