LibraryAPI

dev.libraryapiPublished by libraryapi.devv0.1.3Updated Oct 24, 2026

US public libraries and branches near any address, with collections from the IMLS survey

VerifiedSTDIODesktop onlyLocation & LifestyleData & Analytics

Overview

AI-generated overview

LibraryAPI lets an assistant look up US public libraries and branches by address, coordinates, name, state or city, using federal IMLS survey data.

What you can do
  • Find nearby library branches from a US street address or from latitude/longitude coordinates
  • Search library systems by name, state or city and pull a full system profile by FSCS ID
  • Retrieve the full record for a single branch outlet by its ID
  • Get statewide library totals, such as branch counts and collection sizes
When to use it
Useful when you need US public library locations, branch details, or statewide library statistics — for civic or local apps, neighborhood research, or answering questions about the closest branches to an address.
Requirements
Runs locally as a Python package (pip install libraryapi-mcp or uvx libraryapi-mcp) over stdio. Requires a LIBRARYAPI_KEY environment variable; a free key gives 500 requests per month. Network access to the libraryapi.dev service is needed.
Before you install
The API key is a secret passed via the LIBRARYAPI_KEY environment variable and should not be shared or committed. Requests count against a monthly quota, and address or coordinate lookups are sent to the third-party libraryapi.dev service. Data comes from the IMLS survey and reports hours-open totals, not daily opening times.

Installation

In SourceWeft

  1. Open LibraryAPI in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

libraryapi-mcp

mcp-name: dev.libraryapi/libraryapi-mcp

MCP server for libraryapi.dev — US public library data for AI agents.

Expose library lookups as tools to any MCP-compatible AI assistant (Claude, Cursor, Copilot, etc.). Built on the federal IMLS Public Libraries Survey — public domain, commercially usable.

Installation

bash
pip install libraryapi-mcp

Or run directly with uvx (no install needed):

bash
uvx libraryapi-mcp

Configuration

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

json
{  "mcpServers": {    "libraryapi": {      "command": "uvx",      "args": ["libraryapi-mcp"],      "env": {        "LIBRARYAPI_KEY": "your_api_key_here"      }    }  }}

Cursor / other MCP clients

json
{  "mcpServers": {    "libraryapi": {      "command": "uvx",      "args": ["libraryapi-mcp"],      "env": {        "LIBRARYAPI_KEY": "your_api_key_here"      }    }  }}

Get a free API key at libraryapi.dev — 500 requests/month, no credit card.

Available Tools

ToolDescription
find_libraries_near_addressFind the nearest branches to a US street address
find_libraries_near_coordinatesSame, but from a lat/lng (skips geocoding)
get_outletFull record for one branch outlet by ID
search_librariesSearch library systems by name, state, or city
get_libraryFull system profile by FSCS ID
get_state_summaryStatewide library totals

Systems vs. outlets: a system is the administrative entity (e.g. "Chicago Public Library"); an outlet is an individual branch. Proximity searches return outlets.

Examples

Once configured, you can ask your AI assistant:

"What are the three closest public libraries to 350 Fifth Ave, New York?"

"How many public library branches are there in Vermont, and what's the total collection size?"

"I'm building a civic app — give me every library branch within 5 miles of downtown Chicago as JSON."

Data note

The IMLS survey covers locations, collections, staffing, visits, programs, and finances. It reports hours-open totals (annual, and per week) but not daily opening times — so this API can tell you a branch is open ~45 hours/week, not that it opens at 9am.

Links

License

MIT

Source: README.md at commit 4f38f01

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.3LatestOct 4, 2026
  2. v0.1.2Sep 16, 2026

Score

40% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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
  • License10 pts

    Declare a license in the repository or the registry entry.