Skip to main content
Glama
adathouse
by adathouse

Related Servers

Alternatives to cdgmcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying legislative data from the LegiScan API, including bills and votes, via natural language through an MCP gateway.
      2 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying U.S. legislative data from Congress.gov API using MCP resources for direct lookups and tools for searching and retrieving related data.
      8
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server for the Congress.gov API that consolidates 91 operations into 6 comprehensive legislative tools that can be used by any MCP client (i.e. Claude Desktop), or MCP-compatible AI agent, to query and reason about congressional data.
      4 npm
      1
      JavaScript
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for the Congress.gov API that tracks US federal legislative process, providing tools to search bills and get bill details.
      11
      38 PyPI
      1
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Remote MCP server for nonpartisan U.S. Congress data: plain-language bill decodes (bilingual EN/ES), representative lookup by ZIP with district-office phones, and what's-moving urgency ranking. Read-only, keyless.
      5
      1
      AGPL 3.0
    • A
      license
      A
      quality
      A
      maintenance
      The open Congress.gov MCP server. Provides comprehensive access to the Congress.gov API through 6 organized toolsets, enabling AI systems to retrieve and interact with legislative data from the United States Congress with a clean, unified interface.
      24
      129 PyPI
      32
      Sustainable Use v1.0

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct entity or operation: bill lookup, generic node fetch, arbitrary GraphQL queries, and searches for actions, bills, committees, and cosponsors. No two tools have overlapping purposes.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (e.g., get_bill, search_actions), but graphql_query breaks this by using a noun_noun format. Overall naming is still consistent and predictable.

    Tool Count5/5

    Seven tools is well-scoped for the legislative domain, covering core entities (bills, actions, committees, cosponsors) plus a generic query tool. Not too many or too few.

    Completeness5/5

    The tool set covers bill retrieval, search, and relational data (actions, committees, cosponsors). The graphql_query tool fills any gaps, making the surface effectively complete for read-only legislative data access.

    Maintenance

    ActivityStale
    ResponsivenessNo issues