CongressMCP

com.congressmcpPublished by congressmcp.comOfficial publisherv2.3.0Updated Oct 24, 2026

Federal and 50-state legislative data for AI: bills, text, votes, members, and committees.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

CongressMCP gives an AI assistant access to federal and 50-state legislative data, including bills, bill text, votes, members, and committees.

What you can do
It is a remote MCP server that supplies legislative data covering the U.S. Congress and all 50 state legislatures. According to the description, the data includes bills, bill text, votes, members, and committees. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Useful when an assistant needs to look up legislation, track bills, check roll-call votes, or find legislators and committees across federal and state levels. It suits research, policy, journalism, and civic-information tasks rather than general web search.
Requirements
A remote MCP endpoint at the provider's site, reached over streamable HTTP. Authentication is required via OAuth; no environment variables or headers are declared. Network access to the provider is needed.
Before you install
Access requires OAuth sign-in, so the assistant will act under your account and its permissions. The manifest lists no tools, so what it can read or change is not documented; confirm scope before use. Legislative data may be incomplete or out of date, so verify against official sources.

Installation

In SourceWeft

  1. Open CongressMCP in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.congressmcp%2Fcongressmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "congressmcp": {
      "type": "http",
      "url": "https://www.congressmcp.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2.3.0LatestSep 26, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.