Private beta access
SEC EDGAR MCP server for Claude and Codex
Connect Claude, Codex, or any MCP-compatible workflow to source-aware SEC EDGAR filing metadata for finance research and monitoring.Short answer
CMD+RVL's SEC EDGAR MCP server gives AI agents a bounded way to query filing metadata by company, CIK, form type, date range, amendments, and filing cadence while keeping EDGAR source context visible.- Private-beta remote MCP endpoint
- Claude, Codex, and Claude Desktop examples
- 10-K, 10-Q, 8-K, and amendment metadata
What the EDGAR MCP server covers
The public page keeps the surface deliberately narrow: retrieval, filing history, and monitoring context that a human can check against SEC EDGAR.Source-aware filing metadata
Query companies, CIKs, form types, filing dates, amendments, and cadence with records that point back to EDGAR source context.MCP access for finance workflows
Use a private-beta MCP endpoint from Claude, Codex, or another compatible client when your agent needs current filing metadata instead of pasted documents.Bounded query surface
Designed for retrieval, filing history, and monitoring questions. It is not a general filing validator, investment adviser, or substitute for human review.Example queries
"How many 8-K filings were submitted yesterday?"
"Show me Microsoft's 10-Q filings from Q4 2025"
"List amended 10-K and 10-Q filings for Tesla in 2025"
"What's the filing cadence for JPMorgan over the last twelve months?"
For developers
Technical details about the EDGAR MCP server for finance-data workflows, including the available tool, supported query patterns, and access boundaries.Available tool
edgar_com_query
Natural language query interface to EDGAR filing metadata. Supports counts, lists, statistics, trends, amended-filing checks, cadence analysis, and time windows. Automatically handles date ranges, calendar quarters, and relative dates.Supported query types
count
list
statistics
frequency
trend
time_window
amended
cadence
Request access
The EDGAR MCP server is currently in private beta. Enter your email to request an API key.Quick start
Already have an API key? Follow these steps to connect the EDGAR MCP server to your client.Before you start
- API key: request access above and wait for your API key via email
- Node.js: version 18 or higher installed on your machine
- MCP client: Claude CLI, Codex CLI, or Claude Desktop installed
1
Choose your MCP client
Select the client you want to configure. Each has a different config file location.2
Open your Claude settings file
Open your Claude settings file. If it doesn't exist, create it at the path below.~/.claude/settings.json
3
Add the EDGAR MCP server config
Copy this configuration and paste it into your config file. Replaceyour-api-key with the API key you received via email, and your-session-id with any identifier you like (e.g., "my-session-1").{
"mcpServers": {
"edgar": {
"type": "sse",
"url": "https://edgar.cmdrvl.com/mcp",
"headers": {
"X-API-Key": "your-api-key",
"MCP-Session-ID": "your-session-id"
}
}
}
}4
Restart your client
Start a new Claude CLI session. The edgar_com_query tool should now be available. Try asking: "How many 10-K filings were submitted last week?"Using a different tool?We have instructions for Claude CLI, Codex CLI, and Claude Desktop. If you're using a different MCP-compatible client (Cursor, VS Code, Windsurf, etc.), the configuration pattern is similar. You'll need to point to our SSE endpoint and include your API key in the headers. Reach out and we'll help you get set up.