Skip to main content
The remote MCP server uses Streamable HTTP. It has one tool per endpoint that your connection’s scopes allow, plus time_window to convert local dates and times, and create_job, get_job and get_job_result for async jobs (Growth and up). There are two ways to sign in:
  • OAuth: you sign in to the console and approve one project and its scopes. No key is involved, and you can revoke access from the console at any time. An OAuth connection can call every data tool its scopes allow. It cannot open streams or read your credit balance: use an API key for those.
  • API key: the client sends Authorization: Bearer hdk_sk_... from its own configuration. Never put a key in a prompt.

Set up your agent

The console’s MCP page shows these steps for each client, with a button to copy the setup.
  1. Open Settings, then Connectors, and select Add custom connector.
  2. Name it Hyperdash Data and paste https://data.hyperdash.com/mcp.
  3. Select Connect and sign in with your Hyperdash account.
  4. Choose the project and the scopes, then select Approve access.
The connector is saved to your Claude account, so it works on web, desktop and mobile.
The MCP entry in this page’s menu installs a different server, docs.hyperdash.com/mcp, which searches these docs. The data server is data.hyperdash.com/mcp.

Try it

Open a new chat and ask:
For better results, have the agent read the Data skill first.

Spending limits

Every MCP call uses your workspace’s credits. A connection has no budget unless you set one, so by default an agent can spend up to your balance. MCP results do not show what a call cost; the console’s Logs page shows the credits each request used. To keep an agent inside a budget, open Settings, then Security, then Connected apps in the console, edit the connection and set a credit budget per day or month. A call over any limit is refused without charge, and the error says which limit it hit. See Credits.