Access live U.S. Congressional data — bills, votes, members, committees, hearings, and more — through natural language via the [Model Context
Access live U.S. Congressional data — bills, votes, members, committees, hearings, and more — through natural language via the Model Context Protocol. That is what the congressmcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The server publishes 4 tools. What each one is for:
Toolset — OperationsBills — 16Laws — 2Amendments — 7Configuration is passed through the environment: CONGRESS_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. CongressMCP's toolset — Toolset, Bills, Laws and 1 more — is a fair guide to whether it matches your workflow. It is maintained by amurshak; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against CongressMCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Toolset | Operations |
| Bills | 16 |
| Laws | 2 |
| Amendments | 7 |
{
"mcpServers": {
"congressmcp": {
"command": "uvx",
"args": ["congressmcp"],
"env": {
"CONGRESS_API_KEY": "your-api-key-here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CONGRESS_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.