Skip to main content
Glama
Sign In
libraryapi-mcp

libraryapi-mcp

Official
by library-api
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to libraryapi-mcp

No user-submitted related servers found.

    Related Servers

    • U.S. Census Bureau Data API

      costa5817
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects AI assistants with official U.S. Census Bureau statistics, enabling them to discover available datasets, resolve place names to FIPS geography codes, and retrieve aggregate demographic and economic data through natural language. It draws on both the live Census Data API and a locally seeded database for faster search.
      MIT

    • CDC MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query U.S. public-health datasets such as disease surveillance, mortality, behavioral risk factors, and flu activity through the Socrata API, using natural language or direct tool calls.
      415 npm
      MIT

    • U.S. Census Bureau Data API

      chenle70
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to access official Census Bureau statistics through the Census Data API and other official sources, supporting dataset discovery, geography resolution, FIPS lookup, and aggregate data retrieval.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: get_library fetches system-level data by ID, get_outlet fetches branch-level data, search_libraries finds systems by criteria, find_libraries_near_address/coordinates handle geolocation, and get_state_summary provides aggregates. No two tools overlap in a way that would confuse an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (get_, find_, search_). The naming is predictable and clearly indicates the action and target resource.

    Tool Count5/5

    Six tools is well-scoped for a library data API. Each tool covers a distinct query pattern (lookup by ID, search, geospatial, summary) without unnecessary redundancy or bloat.

    Completeness5/5

    The tool surface covers the core domain tasks: retrieving individual records (library, outlet), searching for systems, finding nearby branches by address or coordinates, and getting statewide summaries. This is a complete set for the apparent purpose of accessing public library statistics and locations.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources