Skip to main content
The Insito MCP server exposes your Insito workspace to AI agents through the Model Context Protocol. Point any MCP client — Claude Desktop, Cursor, or your own — at it, and you can create surveys, publish them, and read NPS analytics just by asking. It’s published on npm as @insito/mcp and runs locally over stdio, so no data leaves your machine except the calls it makes to the Insito API on your behalf.

Requirements

MCP access is a paid feature. On the free plan the Settings → API keys screen shows an upgrade prompt instead of the create form, and any existing key stops working if a workspace drops back to free. Upgrade under Settings → Plan in the dashboard.

Get an API key

The MCP server authenticates with a dashboard API key: a personal access token limited to the permissions you pick when you create it.
Using Claude.ai or another client that supports OAuth? Prefer the remote server with OAuth: there’s no key to copy or store.
1

Open the dashboard

Go to admin.insito.app and open Settings → API keys.
2

Create a key

Give it a name (e.g. “Claude Desktop”), choose its permissions and expiry, click Create key, and copy the generated token. It looks like insk_….
3

Store it safely

You’ll only see the full key once. Treat it like a password. You can revoke it anytime from the same screen.

Permissions

The first three are ticked by default. Delete surveys is off unless you tick it. A key can never reach billing, members, integrations or other API keys, whatever its permissions.

Expiry

Every key expires: after 90 days by default, or 30, 180 or 365 days if you choose. An expired key returns 401 token_expired; create a new one and update your MCP config. A key also stops working if its creator leaves the workspace.
Give each key only the permissions it needs. Don’t commit keys to source control or paste them into shared chats. Revoke a key immediately if it leaks.

Next step

Head to Configure to wire the key into your MCP client, then see the Tools reference for what you can ask.