--- title: "Set up the connector" description: "Configure the Mindtickle MCP connector for your organization, choose a scope-control mode, and understand user authorization." contentType: "guide" url: "https://developer.mindtickle.com/docs/mcp/publish-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](/docs/mcp/popular-ai-clients/) for its setup screens. After setup, users follow [Connect your account](/docs/mcp/connect-your-account/) to authorize their own access. For a programmatic integration using client credentials, see [Build a custom client](/docs/mcp/build-a-custom-client/). ## Server URL Use the following URL pattern when adding the connector in your AI client: ```text https://{mindtickle-instance-url}/mcp ``` For example: ```text 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](/docs/mcp/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 client call the search tool. | | `read:copilot_chat` | `mindtickle_seller_copilot_ask` | Lets the client call the Copilot chat tool. | | `read:rooms` | `find_deals`, `find_companies`, `find_contacts`, `find_rooms`, `fetch_room` | Lets the client call the read-only Digital Sales Room tools. | | `write:rooms` | `create_room`, `edit_room`, `share_room`, `create_contacts` | Lets the client call the Digital Sales Room tools that create or modify data, including sharing a room with a buyer. | ## 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. - If the AI client registered for a refresh token during setup, it can use the refresh token grant to replace an expiring access token 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](/docs/mcp/connect-your-account/): Connect an account after the connector is published. - [AI clients](/docs/mcp/popular-ai-clients/): Follow the setup steps for your AI client. - [Best practices](/docs/mcp/best-practices/): Deploy the connector securely.