src ▸ site opened 0

Turn SEC EDGAR into MCP tools

Give your AI agent SEC EDGAR tools. Writ turns your SEC EDGAR workflows into authenticated MCP tools your agent can call, taking real actions on your own account.

Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
claude_desktop_config.jsonMCP · writ-sec-edgar
json
{
  "mcpServers": {
    "writ-sec-edgar": {
      "url": "https://api.usewrit.app/mcp/your-workspace",
      "headers": { "Authorization": "Bearer wt_8f2c...a91" }
    }
  }
}
MCP server any client authenticated
new ▸ tool minted 01
02
create

No SEC EDGAR MCP server yet? Build one in minutes

Record the SEC EDGAR task once, or describe it to an AI session, and Writ turns it into an MCP tool your agent can call, taking real actions on your own SEC EDGAR account.

  1. 1
    Record a SEC EDGAR action once

    Open the recorder and search filings on SEC EDGAR in a real browser. Writ captures the steps, login and 2FA included, into a workflow.

  2. 2
    Publish it as an MCP tool

    One click exposes the workflow as an MCP tool with a typed input schema, alongside a REST endpoint. Your agent picks it by its description.

  3. 3
    Call it from any MCP client

    Point Claude Desktop, Claude Code, Cursor, or any MCP client at your Writ server. The SEC EDGAR tool acts on your own account and returns structured output.

Browse supported MCP clients, see what's possible on workflows, or search for another site. Free to start. See pricing.

gap ▸ no official mcp 02
03
why

SEC EDGAR has no MCP server

Read-only website-to-MCP tools can summarize a SEC EDGAR page, but they can't do anything on it. Writ turns the SEC EDGAR workflows you build into MCP tools your agent calls to take real actions (search, extract, submit), authenticated, on your own SEC EDGAR account.

Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.

tools ▸ actions named 03
04
named tools

SEC EDGAR tools your agent can call

Each tool is a real SEC EDGAR workflow with a typed input schema and structured output. Your agent picks the right one by its description.

{ }edgar.search_filingsSearch filings by company and type and return the list.

Example tool schema

edgar.search_filings.jsonschema
json
{
  "name": "edgar.search_filings",
  "description": "Search filings by company and type and return the list.",
  "input_schema": {
    "type": "object",
    "properties": {
      "query": { "type": "string", "description": "What to look up on SEC EDGAR." }
    },
    "required": ["query"]
  }
}
wire ▸ any client 04
05
connect

Add the server to any MCP client

Copy the config into your client and authenticate with a wt_ key. Tools appear automatically.

Your key (wt_)
json
{
  "mcpServers": {
    "writ-sec-edgar": {
      "url": "https://api.usewrit.app/mcp/your-workspace",
      "headers": { "Authorization": "Bearer wt_8f2c...a91" }
    }
  }
}
Downstream caller (csk_)
json
{
  "mcpServers": {
    "writ-sec-edgar": {
      "url": "https://api.usewrit.app/mcp/your-workspace",
      "headers": { "Authorization": "Bearer csk_3a90...f4d" }
    }
  }
}
>_

Per-client setup. Step-by-step config for each client lives on the per-client pages: Claude Desktop, Claude Code, Cursor, Windsurf.

auth ▸ logged-in web 05
06
authenticated

Your agent acts on your own SEC EDGAR account

EDGAR pages are public; Writ renders them in real Chromium to capture filing index and document fields cleanly.

PersonasTOTP & mailbox OTP Scoped wt_ / csk_ keysStructured output

EDGAR data is public; respect SEC fair-access rate limits and identify your traffic per their guidance.

faq ▸ questions answered 07
08
faq

SEC EDGAR MCP questions

Is there an official SEC EDGAR MCP server?
SEC EDGAR does not publish an MCP server. Writ lets you turn the SEC EDGAR workflows you build (recorded, described, or discovered) into MCP tools your agent can call. They take real actions, not just read page text.
Are there ready-made SEC EDGAR MCP tools I can install?
Record the SEC EDGAR task once in the recorder, or describe it to an AI session, then publish it. Writ exposes it as both an MCP tool and a REST endpoint, usually in minutes.
How is this different from a read-only website-to-MCP tool?
Most website-to-MCP tools are readability crawlers that return page text. Writ tools act and transact: they log in, fill forms, click, extract, and complete multi-step SEC EDGAR tasks, then return structured output your agent can use.
Does it work with SEC EDGAR login and 2FA?
EDGAR pages are public; Writ renders them in real Chromium to capture filing index and document fields cleanly. Because each MCP tool is a real browser workflow, it runs inside your own authenticated SEC EDGAR session, with TOTP and mailbox-OTP two-factor handled by Personas.
Which MCP clients can use these SEC EDGAR tools?
Any MCP-compatible client: Claude Desktop, Claude Code, Cursor, Windsurf, and others. Point the client at your Writ MCP URL and authenticate with a wt_ key (or a csk_ consumer key for downstream callers).
Is it allowed to use SEC EDGAR this way?
EDGAR data is public; respect SEC fair-access rate limits and identify your traffic per their guidance. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
rec ▸ ready

Give your agent SEC EDGAR tools

Build a workflow, publish it as an MCP tool, and call it from any MCP client. Get started free.