dDatahopdocs
Agents

Connect over MCP

Connect Claude Code, Claude Desktop, Cursor or any MCP client to Datahop with a project API key.

Datahop's MCP server is at https://app.datahop.dev/mcp. It uses the streamable HTTP transport and a project API key.

Agent-first

Give this to your agent. It connects over MCP (or the CLI), learns your data and reports what's interesting, without changing anything until you say so.

1. Create an API key

Settings → API keys & MCP → Create key. Give it a name you'll recognise in the activity log, such as claude-growth-agent, and choose Read & write or Read only. Copy the key (dh_sk_…): it's shown only once. The panel then shows the commands below with your key filled in.

2. Add the server

claude mcp add --transport http datahop https://app.datahop.dev/mcp \
  --header "Authorization: Bearer dh_sk_…"

3. Ask something

"What's our signup → upgrade conversion this month, and where do people drop off?"

The agent starts with project_overview and reads your real event names before it queries. It never guesses them. Descriptions you add under Data make this step much more reliable.

Good to know

  • One project per key. The key decides the project, so tools never ask for one.
  • Your agent only sees what it can use. A read-only key doesn't see tools that change things. A product that's switched off removes its tools. Changes apply on the agent's next call.
  • Reads and writes are labelled, so your client can approve reads automatically and ask before writes.
  • Errors explain the fix, such as "Math "p99" needs mathProperty. Hint: set mathProperty to a numeric event property", so the agent can correct itself.
  • Very large results are cut short with a note to narrow the question.
  • A revoked key stops working immediately.

Tips

  • Start read-only while you see how an agent behaves.
  • Give each agent its own key, so the activity log shows who did what.
  • Ask for dashboards by name. Reading a dashboard returns every card's summary in one call.

On this page