--- title: "Set Up Insider One MCP" slug: "set-up-insider-one-mcp" description: "Covers setting up Insider One MCP with OAuth 2.0 for Claude, Cursor, and Microsoft Copilot, including credentials, permissions, testing, and troubleshooting." tags: ["AI assistant integration", "AI connector setup", "connect Claude to Insider", "insider one mcp", "set up mcp"] updated: 2026-11-04T14:05:54Z published: 2026-11-04T14:05:54Z canonical: "academy.insiderone.com/set-up-insider-one-mcp" --- > ## Documentation Index > Fetch the complete documentation index at: https://academy.insiderone.com/llms.txt > Use this file to discover all available pages before exploring further. # Set Up Insider One MCP Insider One MCP connects your AI client to Insider One's analytics and campaign data through natural language queries and creating drafts. Once connected, you can ask questions about campaign performance and retrieve channel metrics directly from your AI client without switching between platforms. Insider One MCP currently supports the following channels: - **Email** (Campaign and Overall Analytics, Template Library, Campaign and Template Drafts) - **SMS** (Campaign, Overall, Transactional, and OTP/Verify Analytics) - **WhatsApp** (Campaign, Overall, Transactional, and OTP/Verify Analytics, Template Management) - **Web Push** (Campaign and Overall Analytics, Top Metrics) - **Mobile App** (App Push Overall Analytics, InApp Details, Message Center Messages) - **Architect** (Journey Analytics) ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-MNMKK4YW.png) > [!NOTE] > To connect **multiple** Insider One panels to the same AI assistant, refer to [Connect Multiple Insider One Panels to Your AI Assistant](/v1/docs/connect-multiple-insider-one-panels-to-your-ai-assistant). ## Prerequisites Before connecting your AI client to Insider One MCP, review the requirements below for OAuth 2.0 setup. Some requirements vary depending on the AI client you use. - An MCP-compatible AI client, such as Claude, Cursor, or Microsoft Copilot - Insider One Client ID and Client Secret (available in your Insider One [Account Settings](/v1/docs/inone-account-settings)) - Node.js is installed on your machine (not required for Claude Desktop) > [!WARNING] > Create a dedicated key set specifically for your MCP client. Do not reuse existing keys. ## Set up MCP with the OAuth 2.0 method OAuth 2.0 is the recommended authentication method because it supports all available channels and does not require separate API keys for each one. Before connecting your AI client, generate your OAuth 2.0 credentials from Insider One. > [!NOTE] > All Insider One MCP tools are available via OAuth 2.0. ### Generate your OAuth 2.0 credentials > [!WARNING] > Once OAuth 2.0 is enabled and used for a specific API, API key authentication is no longer available for that API, and generating new API keys for it is restricted. If your existing integrations use API keys for the same API, review their authentication requirements before proceeding. For details, refer to [OAuth 2.0 Credentials](/v1/docs/oauth-20-credentials). Generate a **Client ID** and **Client Secret** from the InOne panel by following the steps below. 1. Navigate to **InOne >** **your** **username > Settings > InOne Settings > Integration Settings**. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-74QWRL1Z.png) 1. Scroll to the **OAuth 2.0 Credentials** section and click **Generate OAuth 2.0 Credentials**. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-UBI7RBKU.png) 1. Select the scopes you want to grant. For full MCP functionality, enable all available channels. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-72OOO2Y4.png) 1. Once generated, copy your Client ID and Client Secret and store them securely. You will need these in the setup steps below. > [!WARNING] > Your Client Secret is only shown once. Make sure to save it before closing this screen. ### Claude Desktop (No code required) If you use Claude Desktop, you can connect to Insider One MCP through Claude's built-in Connectors interface. No configuration files or terminal commands are required. 1. Navigate to **Claude** > **Settings** and click **Add**, then select **Browse connectors**. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/base64-converted-image-1783002788687.png) 2. In the Directory, search for Insider One, then select the Insider One connector to add it. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/base64-converted-image-1783002925272.png) 3. Paste your **Insider One Client ID** and **Client Secret** when Claude asks for them, with no leading or trailing spaces, and click **Continue**. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-G997VF38.png) 1. The Insider One authorization page opens. The **Client ID** field is already filled in with the Client ID you entered in Claude. Do not change it. Enter the **Client Secret** of the same credential and click **Save**. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-DJM6UNK8.png) > [!NOTE] > Claude keeps using the **Client ID** you entered in step 3. If you change the **Client ID** on the authorization page, the connection fails with invalid_grant (mcp_token_exchange_failed). 1. Once the connection is established, Insider One MCP becomes available within Claude and provides access to 30 read-only and 8 write/delete tools across supported channels. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-A8XS4ARS.png) ### Cursor and other clients (OAuth via npx mcp-remote) If your AI client does not support the Connectors interface (e.g., Cursor and similar tools), configure the MCP server manually using the settings below. > [!WARNING] > Node.js must be installed on your machine. 1. Get your **Client ID** and **Client Secret** from your Insider One [Account Settings](/docs/inone-account-settings). 2. To add the MCP server, navigate to **Cursor** > **Settings > Tools and Integrations > MCP Tools > Add Custom MCP**. 3. Add the following configuration: ```plaintext {  "mcpServers": {    "insider-one-mcp": {      "command": "npx",      "args": [        "-y",        "mcp-remote",        "https://mcp.insiderone.com/mcp",        "--header",        "Authorization: Bearer YOUR_ACCESS_TOKEN"      ]    }  } } ``` 1. Replace `YOUR_ACCESS_TOKEN` with the Bearer token obtained via the OAuth 2.0 authorization flow using your **Client ID** and **Client Secret**. 2. Fully restart Cursor (or your chosen client) to apply the configuration. ### Microsoft Copilot in Teams (via Copilot Studio) You can connect Insider One MCP to Microsoft Copilot in Teams through Microsoft Copilot Studio. In Copilot Studio, add the Insider One MCP server as a tool to a custom agent, then publish the agent to Microsoft Teams. 1. In **Copilot Studio**, open your agent's **Tools** page, click **Add a tool**, and select **Model Context Protocol**. 2. Enter the following server details: - **Server URL:** `https://mcp.insiderone.com/mcp` - **Authentication type:** OAuth 2.0 3. Configure OAuth 2.0 with the following values: | Field | Value | | --- | --- | | Authorization URL | `https://gw.useinsider.com/oauth2/authorize` | | Token URL | `https://gw.useinsider.com/oauth2/token` | | Refresh URL | `https://gw.useinsider.com/oauth2/token` | | Scope | Leave this field empty. Scopes are defined when you generate the OAuth 2.0 credential in Insider One. | | Client ID | Use the Client ID generated in **Settings > InOne Settings > Integration Settings > OAuth 2.0 Credentials**. | | Client Secret | Use the Client Secret generated with your OAuth 2.0 credential. | > [!WARNING] > Your Client Secret is shown only once when you generate the credential. Store it securely before closing the screen. 1. Publish the agent to the **Microsoft 365 Copilot / Teams** channel. 2. Open the published agent in Microsoft Teams and sign in when prompted. You can then interact with the agent in Teams and use the Insider One MCP tools available to your connection. #### Considerations for Microsoft Copilot - **Panel access:** One MCP connection corresponds to one Insider One panel. To access multiple panels, configure a separate MCP tool or agent for each panel using that panel's credentials. - **Credential scopes:** The tools available to the agent depend on the scopes selected when you generate the OAuth 2.0 credential in Insider One. Select all scopes required for the channels you want the agent to access. - **Microsoft requirements:** Publishing an agent to Teams requires a Copilot Studio license and approval from your Microsoft 365 tenant administrator. - **Token management:** You do not need to configure a separate token refresh mechanism. The Power Platform connection manages the OAuth lifecycle, and users sign in once for each connection. ## Tool Permissions Insider One MCP includes both **read-only tools** and **write tools**. You can control when Claude is allowed to use each tool from the connector's Tool permissions screen: - Read-only tools (Analytics, Campaign Lists, Email Templates) can be set to run automatically. - Write tools (creating or editing templates and campaigns) are set to 'Needs approval' by default. Claude will ask for your confirmation before every write action. You can adjust these per tool at any time from **Settings** > **Connectors** > **Insider One** > **Tool permissions**. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-IN3UCL5J.png) ### If already connected If you connected Insider One before a new capability was released, open the connector's **three dots** menu and select **Refresh tools list** to load the newly added tools. If tools still do not appear, remove the connector entirely and connect again from scratch ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-70H8OGEJ.png) ## Test your connection After completing the setup, run one of the following queries to confirm that your connection is working correctly: - “How many web push notifications were sent in the last 10 days?” ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/base64-converted-image-1780914629032.png) - “Show me SMS sending volume over the last 3 months.” ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/base64-converted-image-1780914631352.png) ## FAQ & Troubleshooting If you encounter issues during setup or connection, review the common solutions below. ### I'm getting a connection error, or the connector stopped working. How do I fix it? A simple **Disconnect** is not enough to reset the connector. Follow these steps to completely remove the existing connection before reconnecting: 1. In Claude, navigate to **Settings > Connectors > Insider One**. 2. Click **Disconnect**, then confirm. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-ALCP284W.png) 3. Open the connector menu (**…**) and click **Remove**. Confirm again to completely clear the existing connector state. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-GGKBOWFM.png) 4. Before reconnecting, generate or locate your OAuth 2.0 credentials in the Insider One panel (**Settings > InOne Settings > Integration Settings > OAuth 2.0 Credentials**). Keep your **Client ID** and **Client Secret** ready. 5. Use one credential for the whole process: the **Client ID** and **Client Secret** you enter in Claude must belong to the same credential you use on the authorization page. You don't need to create a new credential to fix a connection error. If you do create one, remove the connector in Claude and add it again with the new credential. 6. Open **Browse connectors**, find **Insider One**, click **Connect**, and enter your **Client ID** and **Client Secret** when prompted. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-45IGUXY5.png) 7. Verify the connection with a simple prompt, for example: `List my SMS campaigns.` ### Claude shows invalid_grant or mcp_token_exchange_failed after I approve access The Client ID on the authorization page did not match the Client ID saved in Claude. This happens when the Client ID field is changed on the authorization page, usually because a different credential is being used. It can also happen when the Client ID entered in Claude includes a leading or trailing space. 1. In Claude, go to **Settings** > **Connectors** > **Insider One**, click **Disconnect**, then open the **three-dot** (**...)** menu and click **Remove**. 2. Choose the credential you want to use and have its Client ID and Client Secret ready. 3. Add the Insider One connector again and paste that Client ID and Client Secret, with no leading or trailing spaces. 4. On the authorization page, do not change the Client ID. Enter the Client Secret of the same credential. ### I connected earlier, but the newly released tools don't appear. If new Insider One tools are available but do not appear in Claude: 1. Navigate to **Claude** > **Settings > Connectors > Insider One**. 2. Open the **connector** menu (**…**) and select **Refresh tools list**. 3. If the new tools still do not appear, follow the complete reconnection process described in the [previous FAQ](/v1/docs/set-up-insider-one-mcp#faq-connection-error) (**Disconnect > Remove > Connect**). ### Claude created a campaign or template. Did anything go out to my customers? No. Claude only creates **drafts** in your Insider One panel. Campaigns and templates are **never sent, scheduled, or published automatically**. Your team must review and launch every draft from the Insider One panel. In addition, every write action requires your explicit approval in Claude before it is executed. ### Which credentials do I use to connect? Use the **OAuth 2.0 Client ID** and **Client Secret** generated from the Insider One panel (**Settings > InOne Settings > Integration Settings > OAuth 2.0 Credentials**). Refer to [Generate your OAuth 2.0 credentials](/v1/docs/set-up-insider-one-mcp#generate-your-oauth-20-credentials). When generating the credentials, select the **scopes for the channels** you want Claude to access. A tool is available only if the corresponding scope is included in the credential. > [!NOTE] > Insider One recommends creating a **dedicated OAuth 2.0 credential** for your Insider One MCP connection instead of reusing an existing credential. ### Invalid credentials - Double-check your **Client ID** and **Client Secret**. - Ensure you are not reusing keys from another integration. - Make sure the **Client Secret** you enter on the authorization page belongs to the **Client ID** shown there. ### Tools not returning data - Confirm that the relevant channels are active on your Insider One account. > [!NOTE] > If you still have issues, please contact the Insider One team at [support@useinsider.com](mailto:support@useinsider.com). ### Claude Team and Enterprise accounts Insider One is available as an official connector in the Claude directory. If you use a Claude Team or Enterprise account and cannot connect to Insider One, your organization’s Claude or IT settings might restrict which connectors members can use. Before troubleshooting the Insider One connection, check the following with your Claude organization owner or IT team: 1. Confirm whether your organization allows third-party MCP connectors in addition to commonly used integrations such as Google, Atlassian, or Slack. 2. Check whether third-party connectors require administrator approval or consent before members can use them. 3. For Team and Enterprise accounts, confirm that an organization Owner has enabled the Insider One connector in the organization’s Claude settings. > [!NOTE] > Organization-level restrictions vary by Claude workspace. A connection issue on a Team or Enterprise account does not necessarily indicate an issue with the Insider One connector. If you previously disconnected and removed the connector, but Claude redirects you directly to the browser without asking for your new credentials when you reconnect, the issue might be related to your organization’s Claude authentication or connector configuration. Creating another OAuth 2.0 credential does not necessarily resolve this behavior. If the connection still fails after your organization confirms the settings above, collect the **exact error message**, **timestamp**, and **reference ID** shown by Claude, then contact the Insider One team. ## Related - [Insider One MCP Functions](/insider-one-mcp-functions.md) - [Insider One MCP Best Practices](/insider-one-mcp-best-practices.md) - [Insider One MCP](/insider-one-mcp.md)