Supersimple

Appearance

Supersimple MCP server ​

Supersimple exposes its AI as a Model Context Protocol (MCP) server, so you can ask analytics questions about your data straight from Claude, Cursor, or any other MCP-capable AI assistant.

Your favorite AI assistant will naturally pick up "Ask Supersimple" as a tool to use when it sees a question about your data. You get the same answer you'd get inside Supersimple – a written explanation, and (where the assistant supports it) an interactive chart.

Looking to go the other way, and let Supersimple's AI use MCP servers as a data source for Supersimple? See our docs for the Custom MCP integration instead.

Setup ​

All you need is the Server URL – https://app.supersimple.io/mcp. If your MCP client asks, the transport is streamable HTTP.

Authentication happens over OAuth: the first time your client connects, it opens a browser window where you sign in to Supersimple and approve access – your client handles the rest and remembers the session. The AI answers with exactly your access (see Permissions below).

sh
claude mcp add --transport http supersimple https://app.supersimple.io/mcp

The first time Supersimple is used, Claude prompts you to authenticate – run /mcp to open the sign-in flow in your browser.

Once it's connected, your assistant gains an Ask Supersimple tool. Just ask in plain language and it calls Supersimple for you:

Ask Supersimple which customers churned last month and why.

Ask the way you'd ask a colleague – Supersimple resolves the field names, metrics, time ranges and grouping itself from your data model, so you don't need to spell out columns or SQL.

Authenticating with an API token ​

If your client does not support OAuth, you can authenticate with a static API token instead. Head to Account settings → Developers and generate an API token. The token is tied to your own user, so the AI answers with exactly your access. Treat it like a password.

Pass it in an Authorization header:

sh
claude mcp add --transport http supersimple https://app.supersimple.io/mcp \
  --header "Authorization: Token YOUR_TOKEN"

Permissions ​

Supersimple answers using your own permissions, so you only ever see data you already have access to – across every connected data source, not just one. Because the connection carries your identity, two people asking the same question may get different results. If you authenticated with an API token, keep it private (anyone holding it can query with your access) and revoke it anytime from Account settings → Developers.