Set Up Insider One MCP

  • Updated on Jan 16, 2026
  • Published on Dec 18, 2025
  • 4 minute(s) read
Prev Next

This guide explains how to set up Insider One MCP and connect it to an MCP-compatible AI client. By completing the steps below, you can securely enable read-only access to Insider One analytics data through the Model Context Protocol.

Prerequisites

Before setting up Insider One MCP, ensure you have:

  • An MCP-compatible client is installed.

  • Node.js is installed on your machine.

  • Insider One API keys with analytics access: Navigate to InOne > Settings > Integration Settings > API Keys to use one of the existing Analytics API keys or create a new key. For more information, refer to API Authentication Tokens.

    Only users with Administrator permission can generate tokens. If your account is not allowed to complete this operation, you can consult the Insider One team.

    We recommend not to reuse an existing API key. Create a dedicated key set specifically for your MCP client, to reduce risk if an agent attempts unintended actions.

  • Your Insider One Partner ID: To find your Partner ID, go to Settings > Account Settings. The number displayed under the panel name is your Partner ID.

MCP-Compatible Clients

Insider One MCP works with any client that supports the Model Context Protocol, including:

  • Claude Desktop

  • Cursor

  • Other MCP-compatible tools

The setup logic is the same across clients. Differences are noted where relevant.

MCP Server Configuration

To connect your AI client to Insider One MCP, you need to register Insider One as a remote MCP server.

To connect an MCP-compatible client to Insider One MCP, you need to edit the client’s local configuration file and register Insider One as a remote MCP server.

The exact file name and location may vary by client, but the overall structure and required fields are the same.

Required Fields

  • mcpServers: Defines all MCP servers available to the client.

  • mcp-name: A custom name for the Insider MCP server. You can rename it as suitable.

  • command: Uses npx to run the MCP remote connector.

  • mcp-remote: Connects the client to a remote MCP endpoint.

  • <INSIDER_MCP_ENDPOINT>: The Insider MCP server endpoint provided by Insider. (http://mcp.insiderone.com/mcp)

  • headers: Used for authentication and scoping:

    • Channel-specific API keys

    • Partner ID for analytics context

Your MCP client configuration contains sensitive secrets (API keys). Treat the configuration file as a secret:

  • Do not commit it to source control (Git)

  • Do not share screenshots that include keys

  • Restrict file access permissions on your machine

  • Rotate keys immediately if you suspect exposure

  • Use dedicated, least-privilege keys for MCP only

To configure the MCP Server,

  1. Locate the client’s MCP configuration file.

  2. Add a new MCP server entry for Insider One.

Example MCP Server Configuration

{
  "mcpServers": {
    "insiderone-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "<http://mcp.insiderone.com/mcp>",
        "--allow-http",
        "--debug",
        "--header",
        "X-Email-API-Key:<your-email-api-key>",
        "--header",
        "X-SMS-API-Key:<your-sms-api-key>",
        "--header",
        "X-App-Push-API-Key:<your-app-push-api-key>",
        "--header",
        "X-Web-Push-API-Key:<your-web-push-api-key>",
        "--header",
        "X-Partner-Id:<your-partner-id>"
      ]
    }
  }

  1. Replace <your-api-key> with the actual key values from the API Keys page in Settings.

  2. Save the configuration file.

  3. Restart the client.

  4. After the restart, you should locate the Insider One MCP on your client tools.

Rate limits apply based on existing Insider One API policies.

Setup Troubleshooting

This section covers common setup, configuration, and client-side issues you may encounter when using Insider One MCP, along with recommended resolution steps.

Insider One MCP does not appear as an available tool

Possible causes

  • The MCP configuration file was edited incorrectly.

  • The client was not restarted after configuration.

  • The MCP server definition contains a syntax error.

How to resolve

  • Double-check that the configuration file contains valid JSON.

  • Ensure the mcpServers object is correctly defined.

  • Restart the MCP-compatible client completely.

  • Confirm that the Insider One MCP server name is not duplicated.

The permission prompt does not appear

Possible causes

  • The client did not detect a valid MCP server.

  • The question does not require Insider One data.

  • The MCP server failed to initialize.

How to resolve

  • Ask a clear analytics question, define the channel and time.

  • Example: “Revenue by channel last week”.

  • Verify that Insider One MCP is listed as an available tool.

  • Check that the MCP endpoint and headers are correctly defined.

Authentication or Authorization Errors

Possible causes

  • Missing or incorrect API keys.

  • Incorrect Partner ID.

  • The API key does not have analytics access.

How to resolve

  • Verify all required headers are included.

  • Confirm API keys belong to the correct Insider One account and are valid.

  • Ensure the Partner ID matches your Insider One environment.

  • Regenerate API keys if necessary.

Requests are rejected after approval

Possible causes

  • The request exceeds the allowed scope.

  • The requested data is not available for the account.

  • Rate limits are applied.

How to resolve

  • Ensure the request is analytics-only and read-only.

  • Try a smaller time range.

  • Check existing Insider One permissions for the account.

Client Shows Connection or Network Errors

Possible causes

  • The MCP endpoint is unreachable.

  • Network restrictions or firewall rules.

  • Node.js is not properly installed.

How to resolve

  • Verify the MCP endpoint URL.

  • Ensure Node.js is installed and accessible via npx.

  • Check network and firewall settings.

  • Retry after restarting the client.

Cursor-Specific Issues

Insider One MCP is not selectable in the Cursor

  • Ensure the MCP server is added under external tools

  • Restart the Cursor after saving the configuration

Requests do not execute

  • Confirm that you approved the permission prompt

  • Check that the MCP server is selected for the request

Unexpected or Incomplete Results

Possible causes

  • Ambiguous or incomplete questions

  • Missing time ranges

  • Unsupported metrics

How to resolve

  • Be explicit about time ranges and metrics

  • Use Insider One terminology where possible, and define channel type

  • Ask one analytical question at a time

Debugging Tips

  • Enable debug mode in the MCP server configuration

  • Review logs provided by the MCP client

  • Start with simple queries before complex analysis

When to contact the Insider One team?

Contact Insider One team if:

  • The MCP endpoint is accessible but consistently fails.

  • Authentication succeeds, but no data is returned.

  • Errors persist after following the troubleshooting steps.

  • Include the following when contacting support:

    • Client type (e.g., Cursor, Claude Desktop)

    • Error messages or logs

    • Time of the request

    • MCP server configuration (with API keys removed)

Disclaimer: Model Context Protocol (MCP) is a newly introduced open protocol and may be susceptible to security issues or vulnerabilities. Follow your organization’s security policies and review configurations carefully.