SEC EDGAR MCP Server

MCP server for SEC EDGAR data — company filings, financial concepts, and company info. The sec edgar mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 8 defined tools rather than through you.

What it actually does

A Model Context Protocol server that gives Claude Desktop access to SEC EDGAR data — company filings, financial statements, and company info. No API key needed.

Adding it to your client

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

Its toolset

Everything the assistant can do here goes through one of these:

• sec_configure — First-run setup — saves your contact email
• sec_lookup_cik — Resolve a ticker symbol to its SEC CIK number
• sec_company_info — SIC code, industry, state of incorporation, fiscal year end, addresses
• sec_recent_filings — Recent filings (10-K, 10-Q, 8-K, etc.) with direct URLs — pages into older history automatically when a form-type filter needs it
• sec_financial_concept — Historical financial data from XBRL (revenue, net income, EPS, assets…)
• sec_list_tickers — Search/list all SEC-registered tickers with exchange info
• sec_company_facts — Discover all XBRL concepts (metrics) a company reports
• sec_xbrl_frames — Cross-company comparison of a financial metric for a given period

Caveats

• 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.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the sec edgar mcp server does with a few real requests.

When to reach for it

This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. SEC EDGAR's toolset — sec_configure, sec_lookup_cik, sec_company_info and 5 more — is a fair guide to whether it matches your workflow. It is maintained by brechanbech; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.