About Congress Member Votes
An MCP server for exploring U.S. House members’ roll-call votes, attendance, and party-line voting, using records from the House Clerk. It covers the 119th Congress and explains the denominators and cases where figures cannot be computed.
Key features
- 01Retrieve a member’s roll-call positions
- 02Filter by bill or roll range
- 03Calculate attendance and party-line shares
- 04View member positions and party tallies for a roll call
Use cases
- 01Verify a member’s vote on a bill
- 02Compare members’ attendance and party-line shares
- 03Review state or party positions on a roll call
MCP support
The MCP server provides tools to retrieve member vote positions, attendance and party-line measures, and results for individual roll calls.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://gateway.pipeworx.io/congress-member-votes/mcpclaude mcp add --transport http pipeworx-io-congress-member-votes https://gateway.pipeworx.io/congress-member-votes/mcp{"mcpServers":{"pipeworx-io-congress-member-votes":{"type":"http","url":"https://gateway.pipeworx.io/congress-member-votes/mcp"}}}Open in Cursor{"servers":{"pipeworx-io-congress-member-votes":{"type":"http","url":"https://gateway.pipeworx.io/congress-member-votes/mcp"}}}Open in VS Code{"mcpServers":{"pipeworx-io-congress-member-votes":{"type":"http","url":"https://gateway.pipeworx.io/congress-member-votes/mcp"}}}{"mcpServers":{"pipeworx-io-congress-member-votes":{"serverUrl":"https://gateway.pipeworx.io/congress-member-votes/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project README@pipeworx/congress-member-votes
How each U.S. House member voted, how often they were there, and how often they vote with their party, from the U.S. House Clerk's roll-call votes.
Part of Pipeworx — an MCP gateway connecting AI agents to 1875+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
member_vote_positions(bioguide_id | name [+ state], bill?, question_contains?, from_roll?, to_roll?, limit?, congress?, session?)— one member's position (Yea, Nay, Present, Not Voting, or not on the roll) on roll calls, newest first. Answers "how did Rep. X vote on bill Y".member_attendance_party_line(bioguide_id | name [+ state], from_roll?, to_roll?, congress?, session?)— attendance and party-line share for one member over a session or roll range. Every figure carries its denominator and exclusions; a figure that cannot be computed isnullwith a stated reason, never 0% or 100%.roll_call_positions(roll_number, party?, state?, position?, congress?, session?)— every member's position on one roll call, with party tallies.
What the derived figures mean
- Attendance denominator: recorded roll calls in the range on which the member was on the roll. Quorum calls and Speaker elections are excluded (and counted in
excluded_rolls).attended= Yea + Nay + Present;missed= Not Voting. - Not on the roll is not Not Voting. A member absent from a roll entirely (not yet seated, or already gone) is excluded from the denominator and counted separately as
not_on_roll_excluded. with_party_majority: of the member's Yea/Nay votes, the share matching what a strict majority of their own party's Yea/Nay voters did. Includes lopsided votes, so it runs high. Party-tied rolls are excluded and counted.party_unity: the same, restricted to rolls where a majority of Democrats opposed a majority of Republicans.- The Speaker is listed on a roll only when voting, so a Speaker's missed-vote count cannot be derived; attendance is returned as null with that reason (party-line is still computed over the votes cast).
- Party is the member's party at their latest roll call. Independents have no D-versus-R majority, so no party-line figure is computed for them.
Auth
Keyless.
Coverage
House only. 119th Congress, sessions 1 and 2. Other Congresses and the Senate return a named reason. Senate roll-call records could not be read: the Secretary of the Senate's site refused every request (HTTP 403) from this service and from a separate machine on 2026-10-23.
Data sources
- U.S. House Clerk, roll-call votes. US federal data, public domain.
Rolls are held as a compact member-by-roll table, generated by scripts/bake-congress-member-votes.mjs (the refresh path), uploaded at deploy and injected into the pack (pack-baked-indexes.json). Rolls newer than the table are read from the Clerk live on each call (up to 40), so every response states the last roll it covers (rolls_covered), how many were added live (live_topup) and data_as_of. If the live read fails the response says so and covers only the stored rolls.
The Clerk answers a roll that does not exist with an HTTP 200 stub rather than a 404; the pack treats that as "no such roll" and any other non-record body as a fault.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"congress-member-votes": {
"url": "https://gateway.pipeworx.io/congress-member-votes/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/congress-member-votes/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1875+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/member_vote_positions \
-H 'Content-Type: application/json' \
-d '{"bioguide_id":"P000197","bill":"H CON RES 14","congress":119,"session":1}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/member_vote_positions. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"congress-member-votes": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-congress-member-votes"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-congress-member-votes
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Congress Member Votes data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.