MCP server
Connect Datahyena to Claude, Cursor, and any MCP client and query signals in natural language.
Datahyena is available as an MCP server, so you can connect it to Claude, Cursor, Codex, Gemini, or any MCP-compatible client and query funding, acquisition, and executive-move signals in natural language. The tools mirror the REST API exactly. Available on every plan.
Server URL
https://api.datahyena.com/mcpTransport is Streamable HTTP. Authentication is OAuth 2.1 with PKCE: your client opens a browser, you sign in and pick a workspace, and access is granted to that workspace. Revoke a connection any time from the dashboard.
Set up with a prompt
The fastest path: copy this prompt into your agent and let it set itself up. It reads datahyena.com/agents.md and datahyena.com/auth.md and picks MCP or REST based on what the client supports.
Set up Datahyena in this project. Datahyena is a company-event signal API: funding rounds, acquisitions, executive moves, companies, investors, and a single-call company timeline.
1. Read https://datahyena.com/agents.md for the integration guide and https://datahyena.com/auth.md for authentication.
2. If this client supports MCP, add the remote server https://api.datahyena.com/mcp (Streamable HTTP; I will authorize via OAuth in the browser; no API key needed).
3. Otherwise use the REST API at https://api.datahyena.com/v1, reading my key from the DATAHYENA_API_KEY environment variable and sending it in the X-API-Key header. If it is not set, do not ask me to paste the key into chat; tell me to create one at https://app.datahyena.com (50 free credits, no card), set DATAHYENA_API_KEY, and resume.
4. Verify the setup by fetching three recent funding events and summarizing them with their sources.Set up your client
Claude
Claude Code and Claude Desktop.
ExploreCursor
Add Datahyena to Cursor's MCP settings.
ExploreCodex CLI
Add Datahyena to the OpenAI Codex CLI.
ExploreGemini CLI
Add Datahyena to the Gemini CLI.
ExploreOther clients
Any client that speaks remote MCP.
ExploreTools
Each tool maps one-to-one to a public API endpoint, with the same filters and the same response shape.
| Tool | Returns |
|---|---|
funding_events | Funding rounds. Filter by round, amount range, country, industry, vertical, employee size, or company. |
acquisitions | Acquisition and merger events. Filter by payment type, deal amount, merger flag, or company. |
exec_moves | Executive appointments, promotions, departures, and transitions. |
companies | Company records. Search by name, domain, country, industry, employee bucket, or founded year. |
investors | Investor records. Search by name, type, country, or domain. |
company_timeline | One company's full timeline: funding rounds, acquisitions, and executive moves, plus firmographics and investors. Resolve by id, domain, name, or LinkedIn URL. |
Every tool returns the standard API envelope (success, data, pagination, meta), so you get the same records and cursor pagination as the REST endpoints.
Credits
MCP tool calls bill exactly like the API: one credit per record returned, charged only on success. If a workspace is out of credits, the tool returns an error instead of data, and a page is trimmed to what the balance covers. See Credits.
Scopes
Access is granted with read scopes, one per resource: read:funding, read:acquisitions, read:exec_moves, read:companies, read:investors. Approving the default connection grants all of them.