LibraryAPI vs Bowmark

In-depth architectural comparison of the LibraryAPI and Bowmark 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?

L

Choose LibraryAPI when:

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

Explore LibraryAPI Details

Choose Bowmark when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: get_library, run, register.

Explore Bowmark Details

Feature & Specification Comparison

Specification	L LibraryAPI Developer Tools	Bowmark Developer Tools
Summary	US public libraries and branches near any address, with collections from the IMLS survey	Pre-computed navigation recipes for public websites — skip explore-and-discover.
Category & Scope	Developer Tools	Developer Tools
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"
      ]
    }
  }
}

{
  "mcpServers": {
    "bowmark-2": {
      "command": "npx",
      "args": [
        "-y",
        "skills"
      ]
    }
  }
}

Related MCP Server Comparisons