Cursor MCP workflow

SEC Filing MCP Server for Cursor Projects

Add SEC filing tools to Cursor projects through a remote MCP configuration. Run public setup checks first, then use hosted MCP direct access or RapidAPI REST access for production filing watchlists, company lookup, and filing summaries.

Cursor project setup Downloadable MCP config No-key demo runner Production API-key boundary SEC filing watchlists

Run no-key tool calls Request hosted MCP access Subscribe on RapidAPI Open browser demo Download MCP config Remote client setup

Remote MCP setup

{
  "remoteServer": "https://api.data-apis.com/mcp",
  "transport": "streamable-http",
  "publicSetupTools": [
    "sec_demo_latest_filings",
    "sec_subscription_info"
  ],
  "productionTools": [
    "sec_watchlist_changes",
    "sec_company_search",
    "sec_filing_summary"
  ],
  "auth": "x-api-key or Authorization: Bearer for production tools",
  "clientConfig": "https://api.data-apis.com/downloads/sec-event-intelligence-mcp-client-config.json"
}

First no-key MCP checks

Confirm the remote server before sending credentials. The demo call returns a small public SEC filing sample, and the subscription-info call returns pricing, checkout, documentation, and hosted MCP access links.

Open tool-call quickstart Download demo tool call Download subscription-info call Download curl runner

initializeConfirm protocol metadata and tool capability.
tools/listConfirm SEC filing tools are visible before production auth.
sec_demo_latest_filingsRun a no-key public sample response through tools/call.
sec_subscription_infoReturn pricing, REST checkout, hosted MCP access, and configuration links.

Client setup path

Use the hosted MCP endpoint in a Streamable HTTP-capable client or gateway. Production SEC data tools are read-only and require a buyer-controlled API key in request headers.

Client configStart with the generic MCP client config and adapt the secret header for the project.
Project checkConfirm tools/list and the public demo call before adding production credentials.
Production routeUse hosted MCP direct access for client tool calls or RapidAPI for REST snippets and marketplace billing.

When this MCP server fits

The server is designed for filing-monitoring workflows that need normalized public SEC EDGAR metadata without operating a separate ingestion pipeline.

FitCursor projects that need public-company filing metadata
FitDeveloper workflows that want a copyable MCP client config
FitTeams validating remote MCP setup before committing credentials

Production SEC filing tools

After setup checks, authenticated MCP tool calls use the same SEC Event Intelligence data layer as the REST API. Buyers can choose hosted MCP direct access for client tool calls or RapidAPI for REST snippets and marketplace billing.

sec_watchlist_changesPoll grouped ticker watchlists for newly observed filings.
sec_company_searchResolve public companies by ticker, CIK, or company name.
sec_company_filingsFetch issuer filing history and source filing links.
sec_filing_summaryRetrieve one normalized filing record by accession number.
sec_insider_tradesReview public Forms 3, 4, and 5 metadata by ticker.

Data infrastructure only. MCP tools expose public SEC filing metadata only, require buyer-controlled API keys for production data calls, and do not provide trading, rating, recommendation, or personalized financial guidance.