Give your agent US government data

Edgrapi is MCP-native. Point any MCP client at one hosted server and your agent pulls SEC filings, federal contracts, spending, grants and congressional trades — 19 tools, one key, one JSON schema. Works with Claude, Cursor, Cline, or anything that speaks MCP.

Connect your agent — freeREST docs

Connect the hosted MCP server

A remote MCP server speaking JSON-RPC 2.0 over Streamable HTTP. Discovery (initialize, tools/list) is open, so a client sees every tool before you authenticate. Your Bearer key is required on tools/call and meters against your plan exactly like the REST API.

{
  "mcpServers": {
    "edgrapi": {
      "type": "streamable-http",
      "url": "https://api.edgrapi.com/mcp",
      "headers": { "Authorization": "Bearer edgr_your_key" }
    }
  }
}

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "edgrapi": {
      "url": "https://api.edgrapi.com/mcp",
      "headers": { "Authorization": "Bearer edgr_your_key" }
    }
  }
}

Endpoint:  https://api.edgrapi.com/mcp
Transport: streamable-http
Auth:      Authorization: Bearer edgr_...
Discovery: initialize + tools/list are open (no key)

Or install the agent skill

Prefer a local skill over a remote server? Install the SEC toolset from the public repo. It's pure standard library, no dependencies to build.

npx skills add paperandbeyond23-gif/edgrapi-skills --skill edgrapi-full
export EDGRAPI_KEY=edgr_...

Every tool your agent gets

What it looks like in practice

Ask in plain language; the agent picks the tool and gets real data back, not a guess.

• "Find active DoD solicitations for drones in California." → get_opportunities
• "Who won federal contracts from Lockheed last year, and for how much?" → get_awards
• "List open HHS health grants with their CFDA numbers and close dates." → get_grants
• "What did members of Congress trade in NVDA recently?" → get_congress
• "Compute NVIDIA's margins, ROE and debt-to-equity." → get_ratios
• "What did Berkshire add and exit last quarter?" → get_holdings

A real call and response

{
  "count": 1,
  "opportunities": [
    {
      "notice_id": "a1b2c3...",
      "title": "Aircraft component overhaul services",
      "solicitation_number": "FA8100-26-R-0000",
      "agency": "DEPT OF DEFENSE",
      "type": "Solicitation",
      "naics": "336411",
      "posted_date": "2026-09-10",
      "set_aside": "SBA",
      "link": "https://sam.gov/opp/a1b2c3.../view"
    }
  ]
}

The same call is the get_opportunities tool over MCP. Same data, same shape, whether a script or an agent asks.

How billing works for agents

One edgr_ key covers the skill, the MCP server, and direct REST calls. Discovery is free, so listing tools costs nothing.

Each tools/call debits the same credits as its REST twin. And a call that returns no rows — an empty search — is free, so an agent exploring dead-end queries doesn't burn your balance.

Common questions

Which clients work?

Any MCP client. Claude Desktop, Claude Code, Cursor, Cline, and Windsurf are the common ones; anything speaking JSON-RPC 2.0 over Streamable HTTP connects with the config above.

Do I need separate keys for SEC and government data?

No. One edgr_ key reaches all 19 tools across all five sources. Nothing extra to provision for the SAM.gov, USAspending, Grants.gov or Congress tools.

Do I need my own SAM.gov API key?

No. Edgrapi holds the SAM.gov key and system-account burden. Your agent calls get_opportunities with its Edgrapi key and gets normalized JSON — no 10-request-a-day personal-key wall, no 90-day rotation on your side.

Is the government data live?

It's as current as the source. SAM.gov, USAspending and Grants.gov are official public APIs; congressional trades come from House STOCK Act reports and lag the trade by up to 45 days by law.

Get your API keySee pricing