Set up the connector

As an administrator of your AI client’s organization or workspace, add Mindtickle as a custom connector and configure the available scopes. Your AI client must support remote MCP connections over HTTP and the required authentication flow. Follow the vendor instructions in AI clients for its setup screens.

After setup, users follow Connect your account to authorize their own access. For a programmatic integration using client credentials, see Build a custom client.

Server URL

Use the following URL pattern when adding the connector in your AI client:

https://MINDTICKLE_INSTANCE_URL/mcp

For example:

https://example.mindtickle.com/mcp

Replace MINDTICKLE_INSTANCE_URL with your organization’s Mindtickle instance domain. The /mcp path is fixed and must not be changed.

Caution

The URL must use HTTPS and must end with /mcp. Do not use /sse or any other path.

Roles and responsibilities

For an organization-managed connector, administrators configure access and users connect their own accounts. Role names and permissions vary by AI client.

Role	Responsibility	Access level
Organization admin	Add, configure, and manage custom connectors for the entire organization or workspace.	Full
Regular user	Browse available connectors and connect or disconnect their own account.	Limited

Caution

For an organization-managed connector, the administrator or owner adds the connector before members connect their accounts. The required role depends on the AI client. If a rep needs an organization-managed connector, they should contact their admin.

Scope-control modes

The Mindtickle MCP server supports two ways to control which tools the connector exposes. In both modes, end users see an OAuth consent screen before the connector can access Mindtickle. The difference is who decides which tools (scopes) are available to grant.

Setting	User-controlled (default)	Admin-controlled (Client ID and Secret)
What it means	Users choose which tools to authorize on the consent screen from those supported by the Mindtickle MCP server.	You configure which tools are available to users across the entire organization.
Client ID and Secret required?	Not required. Leave the advanced settings blank.	Required. Enter the credentials issued by your Mindtickle Customer Success Manager (CSM) or account team.
Best for	Organizations that want a simple setup and trust users to manage their own access.	Organizations that want to enforce a consistent, restricted scope policy across all users.

For technical details on tools, see Supported tools.

Scopes

A scope grants access to one or more tools. Users authorize access on the OAuth consent screen. In admin-controlled mode, you restrict which scopes are available to them.

Note

Some AI clients, including Claude, refer to scopes as permissions in their own interface. The underlying mechanism is the same regardless of which word a given client’s UI uses.

Scope	Grants access to	Description
read:search	mindtickle_search	Lets the AI client call the search tool.
read:copilot_chat	mindtickle_seller_copilot_ask	Lets the AI client call the Copilot chat tool.
read:rooms	find_deals, find_companies, find_contacts, find_rooms, fetch_room	Lets the AI client call the read-only Digital Sales Room tools.
write:rooms	create_room, edit_room, share_room, create_contacts	Lets the AI client call the Digital Sales Room tools that create or modify data, including sharing a room with a buyer.
read:deals:deal	fetch_deal_guide	Lets the AI client call the Deal Guide tool.
read:calls	find_call, fetch_call	Lets the AI client call the Call AI tools.
read:manager	fetch_manager_team_insights	Lets the AI client call the Manager Insights tool. The user must also have the manager role in Mindtickle.
read:training:ai_tutor	find_tutorial, fetch_tutorial	Lets the AI client call the AI Tutor tools (beta). Available only to companies that have AI Tutor turned on.

Note

fetch_learner_insights needs no scope. It is available whatever scopes you grant, and it returns only the calling learner’s own data.

How the connection works

The custom connector path uses the OAuth 2.0 authorization code grant, typically followed by the refresh token grant to keep the session active:

• When a user clicks Connect and authorizes access on the Mindtickle consent screen, the AI client receives a token representing that user: this is the authorization code grant.
• From here, the AI client manages the token lifecycle automatically, provided it registered for a refresh token when it was set up, the standard behavior for this connection type. When the access token is close to expiring, the client uses the refresh token grant to obtain a new one without asking the user to sign in again.
• The user must reconnect if access is revoked, the refresh token expires, or the client did not register to receive a refresh token.

Note

The AI client manages authentication requests and tokens. Users do not need to copy tokens or construct API requests when connecting their accounts.

Related

• Connect your account: Connect an account after the connector is published.
• AI clients: Follow the setup steps for your AI client.
• Best practices: Deploy the connector securely.