LibraryAPI vs Geo

In-depth architectural comparison of the LibraryAPI and Geo MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose LibraryAPI when:

• You need dedicated capabilities in the Location Services domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• You have access to required keys: LIBRARYAPI_KEY.
• Primary tools included: find_libraries_near_address, find_libraries_near_coordinates, get_outlet.

Explore LibraryAPI Details

Choose Geo when:

• You need dedicated capabilities in the Location Services domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: geocode, reverse_geocode, get_country.

Explore Geo Details

Feature & Specification Comparison

Specification	LibraryAPI Location Services	Geo Location Services
Summary	US public libraries and branches near any address, with collections from the IMLS survey	Geo MCP — geographic utilities from free public APIs
Category & Scope	Location Services	Location Services
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

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

{
  "mcpServers": {
    "geo-2": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-geo"
      ]
    }
  }
}

Related MCP Server Comparisons