Revelata DeepKPI MCP Server

Revelata DeepKPI MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Deep fundamental data from SEC filings, including operational KPIs not found on Bloomberg, built for your financial AI agents.

What you get

The skills cover a growing set of fundamental workflows for equity research: KPI lookup, filing-text retrieval, derived metric calculation, peer benchmarking, seasonality analysis, and analyst-report pressure-testing.

What the assistant can call

Once Revelata DeepKPI is connected, these are the calls the assistant has available:

• Skill — What it does
• kpi — Pulls structured KPI time series for US public companies from SEC filings; supports Excel export
• company-summary — Describes a company's business and segment / geography structure; supports thematic "who does X?" discovery
• filing — Pulls clean SEC filing markdown into chat; extracts verbatim quotes from MD&A, risk factors, footnotes
• seasonality — Computes seasonal quarterly ratios from historical actuals; splits annual forecasts into quarterly estimates; outputs an Excel workbook
• implied-metric — Derives metrics that aren't directly reported — Q4 from FY−(Q1+Q2+Q3), segment remainders, per-unit economics (ARPU, ASP, AUV), take rates
• pressure-test — Pressure-tests analyst reports against SEC filing data; outputs an interactive HTML report with claim-by-claim evidence and provenance hyperlinks
• benchmark — Performs operational peer / comp discovery via deepKPI semantic search; aligns KPI fingerprints, generates segment sub-benchmarks, supports HTML and
• ideas — Guides users without a specific company or thesis through idea generation — interactive interview, screen, and deep-dive
• revelata — Orchestrates complex multi-step research that crosses multiple workflows
• OpenClaw — OpenClaw uses the deepKPI REST API (no MCP). Get an API key at revelata.com/ai-credits, then:

Configuration and credentials

You will need one environment variable: DEEPKPI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Revelata DeepKPI's toolset — Skill, kpi, company-summary and 8 more — is a fair guide to whether it matches your workflow.

This entry was verified against Revelata DeepKPI's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Revelata DeepKPI.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the revelata deepkpi mcp server does with a few real requests.