Native Insyder MCP

Connect your AI assistant to your Insyder workspaces. The native MCP provides all 51 public API operations as tools: read leads and analytics, update lead details, manage products, record purchases, and create exports, within the permissions you approve.

This is the MCP for working with your data. The separate Documentation MCP searches these guides and explains the API; it cannot access or change your workspace data. You can connect both, using the names Insyder Native and Insyder API Docs to tell them apart.

You need an Insyder account with access to a workspace, and permission to add custom connectors in your assistant. Claude's hosted connector and ChatGPT in a browser use OAuth sign-in. The ChatGPT desktop Add MCP server form uses a personal Insyder API key. Neither setup needs a local bridge, Node.js installation, or tunnel.

Use this server URL:

https://api.insyder.io/mcp

For OAuth, sign in with your existing Insyder account when prompted, choose a workspace, and select Allow access. Read-only access is selected by default. Enable the additional requested actions only if you want the assistant to make changes or create exports. Your assistant receives the data returned by the tools you permit.

Use Claude's hosted custom connector. You can add it through your Claude account and use it in Claude Desktop.

1. Open Claude and go to Customize > Connectors > Add custom connector.
2. Name it Insyder Native, enter https://api.insyder.io/mcp, and select Continue.
3. Keep the detected Sign in now and Use Claude’s published identity settings, then select Add. On the connector page, select Connect. Sign in to Insyder, choose the workspace and permissions, and select Allow access. No client ID or secret is needed.
4. Enable Insyder Native in your conversation's + > Connectors menu. Ask “Use Insyder Native to list my accessible workspaces.”

For Team and Enterprise, an owner first adds the URL under Organization settings > Connectors > Add > Custom > Web. Each member then selects Connect to approve their own Insyder access. See Claude's custom connector instructions.

If you previously used claude_desktop_config.json, disable that local Insyder entry after verifying this connection so duplicate tools do not appear. The optional API-key bridge remains available for local-only clients.

Follow these steps if your Plugins page has Plugins / Apps / MCPs / Skills tabs. This connection uses an API key. To connect by signing in to Insyder instead, follow ChatGPT in a browser below.

1. Create an Insyder key. In Insyder, open Preferences > API access > Create a key. Set Key name to ChatGPT, choose Read only, and select the workspace you want to use. Select Save, then Copy. The full key is shown only once.

2. Open the MCP form. In the ChatGPT desktop app, go to Plugins. Click Add at the top right, then Add MCP server.

   

3. Fill in the connection. On Connect to a custom MCP, enter Insyder Native in Name, then select Streamable HTTP next to Type. This replaces Command to launch with the URL field. Fill the form exactly as follows:

   Field	What to enter
   Name	Insyder Native
   Type	Streamable HTTP
   URL	https://api.insyder.io/mcp
   Bearer token env var	Leave empty
   Headers — Key	X-API-Key
   Headers — Value	Paste the full Insyder key you copied, starting with insyder_live_
   Headers from environment variables	Leave empty

   Paste the key only into Headers > Value, without adding Bearer before it. Keep it out of chat messages.

   

4. Save and restart. Click Save at the bottom right, then Restart when ChatGPT offers it. In Plugins > MCPs, keep Insyder Native enabled.

5. Try it. Start a new conversation and send:

   Use Insyder Native to list my accessible workspaces.

   ChatGPT should return the workspace you selected for the key. You can now ask it to read leads, products, or analytics. To allow changes or exports later, edit the key's permissions in Insyder > Preferences > API access.

Insyder currently supports OAuth for hosted ChatGPT connections; the desktop MCP connection above uses the X-API-Key header. For more about the desktop form, see OpenAI's desktop MCP guide.

Use this separate setup at chatgpt.com to connect with your Insyder sign-in.

1. Open Settings > Security and login and turn on Developer mode.
2. Open ChatGPT Plugins and select + to add an MCP connection.
3. Enter Name: Insyder Native, Description: Read and manage my Insyder workspace data, and the public URL https://api.insyder.io/mcp under Connection. If authentication options appear, select OAuth and leave the optional client ID and secret empty.
4. Create the connection. Sign in to Insyder, choose a workspace, review the permissions, and select Allow access.
5. Start a new conversation, add Insyder Native from the tools menu, and ask “Use Insyder Native to list my accessible workspaces.”

If Developer mode or + is unavailable, your account or workspace policy may restrict custom connections. A workspace administrator may need to enable them. See OpenAI's browser MCP instructions.

Clients with custom HTTP headers can use a personal API key:

Create a key under Insyder > Preferences > API access, select its workspaces and permissions, and save it when displayed. Use the client's private secret storage for the header. Never paste credentials into a chat message or put them in the server URL. See API-key authentication.

OAuth client onboarding currently supports hosted ChatGPT and Claude. Other clients should use the API-key connection unless their OAuth integration has been enabled by Insyder. Send only one authentication method per request.

The native URL ends in /mcp, not /v1/mcp or /sse. Authentication applies to tool discovery and calls. The server is stateless and supports legacy MCP clients and the 2026-07-28 protocol; opening the URL in a browser is not a connection test.

For a client that only accepts local mcpServers configuration, install Node.js LTS and use the mcp-remote bridge. This optional setup runs on your computer. The Claude and ChatGPT setups above do not use it.

{
  "mcpServers": {
    "insyder-native": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@0.13.5",
        "https://api.insyder.io/mcp",
        "--transport",
        "http-only",
        "--silent",
        "--header",
        "X-API-Key:${INSYDER_API_KEY}"
      ],
      "env": {
        "INSYDER_API_KEY": "YOUR_INSYDER_API_KEY"
      }
    }
  }
}

Replace YOUR_INSYDER_API_KEY with your saved key in the private configuration file; leave ${INSYDER_API_KEY} unchanged. Fully restart the client. Use an absolute npx path if it is not on the client's PATH. Closing the local bridge stops this connection.

Try these requests after listing your workspaces:

• “For workspace @mybrand, show 20 uncontacted leads with a score of at least 80.”
• “Summarize the revenue and lead funnel for @mybrand this month.”
• “Show the products in @mybrand, including archived products.”
• “Update this lead's notes to ‘Requested a callback tomorrow’.”
• “Prepare an export of the leads in @mybrand and retrieve the download link when it is ready.”

The last two requests require the corresponding write/export scopes. The assistant should use the account_id returned by listAccounts; a workspace's username is not its API identifier.

The catalogue lists every tool, including tools your connection cannot execute. The API checks permissions on each call. OAuth disconnection, key revocation, expiry, workspace access, and membership changes are checked on each request. MCP uses the same API limits, including the shared per-user rate limit; it does not grant extra access.

Imported data and system-derived facts remain read-only. Neither MCP adds provider credentials, connection management, synchronization controls, analysis triggers, or other operations absent from the public API.

Each tool name matches an operationId in the API reference, with the same parameters and responses.

Most assistants build tool arguments for you. For custom integrations, API path and query parameters become top-level arguments, JSON payloads go inside body, and Idempotency-Key becomes idempotency_key. Array filters stay JSON arrays.

Example arguments for listLeads:

{
  "account_id": "WORKSPACE_ID",
  "status": ["uncontacted"],
  "min_score": 80,
  "limit": 20
}

Example arguments for updateLead:

{
  "account_id": "WORKSPACE_ID",
  "lead_id": "LEAD_ID",
  "body": { "notes": "Requested a callback tomorrow" }
}

Tools return both JSON text and structured content containing the API's status, operational headers, and unchanged response body:

{
  "status": 200,
  "headers": { "x-request-id": "REQUEST_ID" },
  "body": {
    "data": [],
    "meta": { "request_id": "REQUEST_ID", "has_more": false, "next_cursor": null }
  }
}

• Pagination: pass body.meta.next_cursor as cursor, keeping the same filters. Collections default to 50 items, with a maximum of 200; smaller pages can be easier for assistants to handle.
• Writes: createProduct, createPurchase, and createExport require idempotency_key. If a call's outcome is uncertain, retry with the same key and identical body. The API retains idempotency records for 24 hours.
• Exports: call createExport, then poll getExport until ready. Use the returned temporary download links before they expire. deleteExport cancels/deletes an export.
• Errors: API failures set isError: true and preserve the API's problem response. Invalid tool arguments are rejected before dispatch. A successful deletion may return status 204 with body: null.

In Insyder > Preferences > API access > Connected assistants, select Disconnect next to the connection. This immediately blocks its access to Insyder. You can also remove the connector in Claude or ChatGPT. Other connections and your Insyder login remain active.

To change the workspace or permissions, disconnect and connect again. If you use an API-key client, revoke or edit its key under API access, and update the private client configuration after rotating it.