Connect

How to give Claude access to SEC filings (free MCP server)

Claude is a strong reader and a poor librarian. It can dissect a 10-K you paste in, but it cannot browse EDGAR, and if you ask it to recall the exact items in a company’s last 8-K it will often invent them. The fix is to stop relying on its memory and hand it a tool that returns real filings. Here is how to do that in about a minute.

The short version

  • Claude can’t crawl EDGAR and hallucinates specific filing details from memory.
  • The Model Context Protocol (MCP) lets Claude call external tools. Point it at a markets MCP server and it queries real SEC data instead of guessing.
  • Setup is one JSON block (Claude Desktop) or one command (Claude Code), both using a free sk-live key.
  • Once connected, ask in plain English: “recent 8-Ks for NVDA”, “insider buying at small-cap biotechs”, “Berkshire’s latest 13F changes”.

Why Claude can’t just read EDGAR

The SEC’s EDGAR system is public and free, which makes it tempting to assume any capable model can simply read it. In practice there are three walls.

It can’t browse. Out of the box, Claude has no live internet access to fetch a filing index, walk to the right accession number, and download the document. Even with browsing enabled, EDGAR is a thicket of raw HTML, SGML headers and XBRL instance documents that is hostile to ad-hoc scraping.

It hallucinates specifics. Ask a model what items were in a company’s most recent 8-K, or what an insider’s last Form 4 transaction price was, and it will answer fluently. The answer is frequently wrong, because the model is reconstructing a plausible filing rather than retrieving the real one. For research where the number matters, plausible is worse than nothing.

Filings are structured, not prose. A 13F is a table of holdings. A Form 4 is a set of transaction rows. Squeezing those through a chat window as pasted text loses the structure that makes them queryable. You want Claude to be able to ask “which managers added this name last quarter” — that is a database question, not a reading-comprehension question.

The mental model: don’t make the model be the database. Keep Claude as the reasoning layer and give it a tool that is the database. That separation is exactly what the Model Context Protocol was designed for.

What MCP is, briefly

The Model Context Protocol (MCP) is an open standard from Anthropic for connecting AI assistants to external tools and data. An MCP server exposes a set of tools; an MCP client (Claude Desktop, Claude Code, Cursor, ChatGPT’s developer mode) lets the model discover and call them. The model decides when to call a tool and with what arguments; the server does the actual work and returns structured results.

For SEC data, this means you register one server once. From then on, whenever you ask Claude a markets question, it can reach for the right tool — search filings, pull fundamentals, list insider trades — and answer from real data. We cover what makes a good markets MCP server in a separate post; here we focus on getting Claude wired up.

Step 1 — get a free key

ClawTerminal is a markets-research MCP server: SEC filings, fundamentals, prices, macro, crypto and more, behind a single endpoint. It is in free closed beta. Sign in with a magic link — email only, no password — and your personal sk-live-... key is shown after you verify. That key is the credential; the same key works in every client below. The placeholder sk-live-... below stands in for your real key.

Step 2a — connect Claude Desktop

Open your Claude Desktop config file and add a clawterminal entry under mcpServers. The file lives at:

// macOS:    ~/Library/Application Support/Claude/claude_desktop_config.json
// Windows:  %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "clawterminal": {
      "type": "http",
      "url": "https://mcp.clawterminal.ai",
      "headers": {
        "Authorization": "Bearer sk-live-..."
      }
    }
  }
}

Replace sk-live-... with your key, save, and restart Claude Desktop. The tools appear in the connector list.

Step 2b — connect Claude Code

If you live in the terminal, Claude Code takes a single command — no JSON editing:

# Adds the server project-wide
claude mcp add --transport http clawterminal \
  https://mcp.clawterminal.ai \
  --header "Authorization: Bearer sk-live-..."

# Verify it registered
claude mcp list

That writes the server to your Claude Code config. The next session can call every tool the server exposes.

No header field? Some GUI clients (ChatGPT Developer Mode, Claude Desktop’s custom connector dialog) don’t let you set an Authorization header. For those, put the key in the URL instead: https://mcp.clawterminal.ai/k/sk-live-.../mcp with auth set to “none”. Treat that URL like a password — it is the credential.

Step 3 — ask in plain English

Now you talk to Claude normally. When a question needs SEC data, it picks the matching tool and queries the live database. A few examples, and what fires under the hood:

You ask ClaudeWhat it callsWhat comes back
“What were the recent 8-Ks for Nvidia?”list_filings_universalDated 8-K list with item codes, links to documents
“Has anyone been buying insider shares at small-cap biotechs?”cluster_insider_buysForm 4 open-market buy clusters with insider roles and values
“Show Berkshire’s 13F changes last quarter.”fund_holding_changesAdds, trims and exits with position sizes
“What’s Apple’s trailing free cash flow?”get_fundamentalsXBRL companyfacts series, TTM-aggregated
“Find 8-Ks that mention a CEO resignation this month.”search_filingsSemantic search over the 8-K corpus

You don’t memorize tool names. ClawTerminal also ships a resolve_entity tool that turns any ticker, CIK, company name, CUSIP or accession number into a canonical id first, plus a search_tools meta-tool so the model can find the right capability by intent. Claude chains them itself.

What Claude can reach once connected

The SEC surface alone covers the forms that actually move research:

  • 8-K — current reports, semantically searchable, with price-reaction studies around the event.
  • 10-K / 10-Q — section-aware narrative search across risk factors, MD&A and business descriptions.
  • Form 4 — insider transactions, with cluster-buy detection and top-buyer/seller rankings.
  • Schedule 13D / 13G — beneficial ownership and activist stakes.
  • 13F-HR — institutional holdings and quarter-over-quarter changes.
  • N-PORT — fund holdings, returns and debt exposure.
  • DEF 14A — proxy statements and executive compensation.
  • S-1 / 424B — IPO prospectuses.

And because it is a full markets terminal, the same connection also gives Claude XBRL fundamentals, split-adjusted prices and dividends, FRED macro series, crypto perps and prediction markets — so a filings question can flow straight into a valuation or a price-reaction check without switching tools.

Real data still needs judgment. A tool returning the right number doesn’t make the interpretation right. Insider clusters carry IPO/PIPE noise; 13F is 45 days stale; congressional trade values are bucket midpoints. Claude querying real filings is a huge upgrade over recalling fake ones — but the analysis still belongs to you. Our playbook posts spell out the filters for each surface.

That’s it

Two minutes of setup converts Claude from a model that describes filings from memory into one that retrieves them. The model stays the same; you’ve simply stopped asking it to be the database. Once the data is real, the interesting work begins — which is what the rest of this blog is about.

Frequently asked questions

Can Claude read SEC filings on its own?

Not reliably. Claude can summarize a filing if you paste the text, but it cannot browse EDGAR, and asking it to recall specific filing details from memory often produces confident but wrong answers. Connecting it to an MCP server that serves real, structured SEC data removes the guesswork.

Is connecting Claude to SEC filings free?

Yes. ClawTerminal is in free closed beta. You sign in with a magic link, get an sk-live key, and add the MCP endpoint to Claude Desktop or Claude Code. There is no cost during the beta.

Which SEC forms can Claude query?

8-K, 10-K, 10-Q, Form 4 insider transactions, Schedule 13D/13G, Form 13F-HR, N-PORT, DEF 14A proxy and S-1/424B IPO prospectuses — plus XBRL fundamentals and split-adjusted prices.

Does this work with Claude Code as well as Claude Desktop?

Yes. Claude Desktop uses a JSON config entry; Claude Code uses a single claude mcp add command. Both speak the same HTTP MCP transport with a Bearer key. Full setup for Cursor, Codex and ChatGPT is here.

Give your Claude real filings

Free closed-beta key, one MCP endpoint, 160+ markets tools. Sign in with email and connect in under a minute.