The Qobra MCP server is enabled per company by a feature flag — ask the
Qobra team to turn it on for your workspace. Every tool is read-only and
scoped to your Qobra user’s permissions.
What these pages document
Each tool page describes a tool’s inputs and the shape of what it returns. These are MCP tools, not REST endpoints: you never call them over HTTP yourself — you connect an MCP client (Claude, ChatGPT or Dust) to the server, and the model calls the tools for you. ThePOST /mcp/tools/<name>
shown on each page is only how we render a tool’s request and response schema.
Available tools
Every tool is read-only (it never modifies your data) and scoped to the authenticated user’s company and role-based permissions. Today the server exposes:Reading a sandbox
Every tool reads your company’s live environment (its real compensation data) by default. If your company uses sandboxes and your role can read them, calllist_sandboxes to discover
them, then pass a sandbox’s id as the sandbox_id argument of a list tool
(list_plans, list_quotas, list_statements, list_statement_periods,
list_reports, list_dashboards) to read that sandbox instead. sandbox_id
only accepts a sandbox’s id — never a sandbox name, and never the live
environment’s own id (omit the argument to read the live environment).
Tools that take a resource id — such as get_plan, get_statement or
get_report — need no sandbox_id argument: the id itself names the
environment the resource lives in.
Connect an MCP client to Qobra
Prerequisites, the OAuth consent flow, and how to add the server to Claude,
ChatGPT or Dust.