Supper's MCP
Give any AI the ability to answer questions about your business.
Same semantic model · Same verified answers · Available wherever you work with AI
Most business processes aren't one question. They're a sequence: pull this data, combine it with that source, apply some business logic, format the output. Supper Skills automate the sequence so you can build once and run on demand or on a schedule, and get consistent results every time.
Built on
Open MCP standard
OAuth authentication
Inherited permissions
Full audit trail
SOC 2 Type II
What is MCP, in plain English?
A universal plug between AI and your data.
MCP — the Model Context Protocol — is an open standard that lets AI assistants connect to external tools and data sources in a structured, secure way. Think of it as a universal plug: instead of every AI tool building a custom integration with every data source, MCP defines a common language any compliant AI can use to call any compliant tool.
Supper is a compliant tool.
When you connect Supper to an MCP-compatible AI, that assistant can ask Supper questions, retrieve data, and surface answers — all grounded in your semantic model, validated by your accuracy layer, and governed by your existing permissions.
Three connections
One server. Every AI you already use.
Whether you ask questions in Claude, build apps with Claude Code, or run agents in your own stack — the same Supper, the same answers, the same governance.
Ask Claude about your real business data.
Two-minute setup. No code. Verified answers inside the conversation you're already having.
Build apps on top of verified data.
Query live data from your dev session. Validate the shape, then harden the working query into your endpoint.
For developers & data engineers
Plug Supper into any agent stack.
If a tool speaks MCP, it speaks Supper. ChatGPT, Glean, LangChain, CrewAI, your internal Slack bot — all the same.
Ask your AI assistant about your actual business data.
If you're using Claude, connecting Supper takes two minutes. Once connected, Claude can answer questions about your live business data - not a hallucinated approximation, but a verified answer pulled through Supper's semantic model.
Ask Claude "what was our net revenue retention last quarter?" and it calls Supper. Supper runs the query. The answer comes back accurate, auditable, and calculated exactly the way your team has defined it. You never leave the conversation.
Ask data questions inside Claude, without switching tools.
Answers grounded in Supper's semantic model - not a best guess.
Governed by your existing Supper permissions.
Quick start · 15 minutes
01
Open Claude → Customize →Connectors
Find Supper in the connectors list.
02
Connect and authenticate
One-click OAuth — no API keys or config files.
03
Start asking questions
Ask Claude anything about your Supper-connected data.
Build apps on verified data — without writing the data layer yourself.
If you're building with Claude Code, Supper's MCP is already available as a connected tool. You can query your live business data directly from your development session — test questions in plain English, see real results, and harden working queries into your application code.
The workflow: ask Supper a question in plain language, confirm the data looks right, then build your endpoint around the exact query that works. No schema guessing, no test fixtures, no mocking.
Plug Supper into any AI stack that speaks MCP.
Supper follows the open MCP standard. If a tool supports MCP, it supports Supper. Internal Slack bots, sales automation agents, custom reporting tools — any of them can query Supper and get verified business data back.
What Supper exposes over MCP
ask
Ask any data question in natural language. Returns a verified answer grounded in your semantic model.
get_pipeline_status
Check whether a query is still processing or has returned data. Poll this after ask for complex queries.
get_answer_rows
Retrieve structured row data from a completed answer - columnar format, ready to act on.
get_context
Retrieve semantic model context — metric definitions, entity descriptions, available tables.
Your permissions travel with your data.
When an AI agent calls Supper through MCP, it operates within the same permission boundaries as the authenticated user. If a user can't see a table in Supper, an agent calling Supper on their behalf can't see it either.
FAQ
Do I need to be a developer to use Supper's MCP?
No — connecting Supper to Claude as a business user is a two-minute process with no code involved.
Which plans include MCP access?
MCP access is available on Scale and Enterprise plans.
Can I connect multiple Supper organizations?
Claude can only be connected to one Supper org at a time.
Are conversations logged?
Yes — messages that flow between Claude and the Supper agent are stored and visible in app.supper.co.
How does authentication work for backend integrations?
For Claude and Claude Code connections, authentication is handled via OAuth — no API keys or config files required.
What happens to my data when an agent calls Supper?
The same thing that happens when a human calls Supper: the query runs against your live data sources under the authenticated user's permissions, the result is returned, and the exchange is logged in Supper's audit trail.
Ready to connect?
Business users: connect in two minutes and start asking questions. Developers: request the docs and we'll walk you through the integration.