MCP server
The same financial data as 10 tools your agent can call directly. No key to paste — MCP clients sign in through the browser.
What it is
Model Context Protocol is how an agent discovers and calls tools. Point a client at the endpoint below and drillr’s tools appear inside it — the agent decides which to call, and the answers come back with the filings and tables they came from.
https://gateway.drillr.ai/mcp/dataStreamable HTTP transport. Authentication is browser OAuth: the first call opens a sign-in page, and the client keeps the grant afterwards.
Set up your client
Pick what you are holding. Every client below connects to the same server with browser sign-in; no key to paste.
Let your coding agent do it
Paste this into whatever you already have open — Claude Code, Codex, Cursor, anything with a shell. It works out which client it is and walks you through the browser sign-in.
Please install the drillr MCP server for me and walk me through the sign-in: server drillr-data, url https://gateway.drillr.ai/mcp/data, auth browser OAuth.
Use my client's own MCP command to add it (claude mcp add / codex mcp add / my editor's MCP config — whichever applies to you). Then tell me the steps that are mine: MCP tools only load at startup so I'll need to restart, and the browser Allow click is mine to make. Per-client details if you want them: https://drillr.ai/developer/mcp-install.md Reply in the language I'm using with you.Or set it up yourself
The command, config, and steps for each client.
codex mcp add drillr-data --url https://gateway.drillr.ai/mcp/dataWhat happens next
- 1The command prints an authorization URL and waits — open it, sign in, click Allow.
- 2Exit Codex and start a new session. MCP tools load at startup.
- 3Ask “Use drillr-data to look up the ticker for Apple” to confirm it works. That call is free.
If it exits without authenticating
codex mcp login drillr-dataNo API key is required for drillr-data. Your client opens drillr in the browser; sign in if needed, review the named client, and click Allow.
Tools
10 tools. Between them they cover discovery, filings, signals and arbitrary SQL over the financial tables — which is why the set stays small: the agent composes them rather than picking from fifty.
Company
2 toolsTurn a name or a description into tickers. Every other tool wants a ticker.
Filings
2 toolsUS, CN and JP company-filed reports. List first, then search.
Datasets
3 toolsRead-only SQL over the financial, market and alt-data tables. Discover, inspect, then query. The core equity tables reach US, CN and JP; specialized tables can be narrower, and each one states its own coverage.
Signal
3 toolsCompany and market signals from structured earnings-call research and news.
What to ask
You do not call the tools yourself; you ask the agent and it does. Questions that work well are the ones a junior analyst could act on:
- “What does NVDA’s latest 10-Q say about supply commitments?”
- “Japanese manufacturers with net cash and rising free cash flow.”
- “Compare gross margin across the three largest memory makers, last eight quarters.”
- “Which companies disclosed an auditor change this quarter?”
Errors
A failed call reaches your client in one of four shapes. Each tool’s page says which shape its own failures take, and what the message means.
- Invalid arguments
- JSON-RPC error -32602 before the tool runs, listing each bad field. Not charged.
- Credits exhausted
- JSON-RPC error -32001 before the tool runs, with balance and pricing link. Not charged.
- Tool failure
- The tool ran and could not answer: a result marked isError whose text is the message.
- Service unavailable
- JSON-RPC error -32002 — a backend is down. Retry later. Not charged.
Per-tool rates
REST and MCP draw from the same credits wallet. Requests rejected before data retrieval are not charged; see Pricing for plans and current credit options.
Free
Usage-based
Per call
Per call
Free
Free
Per call
Per call
Per call
Per call