MCP Open Library

Created By
8enSmitha year ago
A Model Context Protocol (MCP) server for the Open Library API that enables AI assistants to search for book and author information.
Overview

What is MCP Open Library?

MCP Open Library is a Model Context Protocol (MCP) server designed for the Open Library API, enabling AI assistants to search for book and author information efficiently.

How to use MCP Open Library?

To use MCP Open Library, clone the repository, install the dependencies, and run the server. You can interact with the server using an MCP-compatible client or the MCP Inspector for testing.

Key features of MCP Open Library?

  • Book Search by Title: Retrieve detailed information about books using their titles.
  • Author Search by Name: Find authors by their names and access relevant details.
  • Structured Response Format: Provides consistent JSON responses for easy integration.
  • Error Handling: Includes validation and error reporting for robust usage.
  • Testing: Comprehensive test coverage to ensure reliability.

Use cases of MCP Open Library?

  1. Integrating book search functionality into AI assistants.
  2. Providing detailed author information for educational applications.
  3. Enabling developers to build applications that require book and author data.

FAQ from MCP Open Library?

  • Can MCP Open Library be used with any AI assistant?

Yes! It is compatible with any MCP-compatible AI assistant or client.

  • Is there a demo available for testing?

Yes! You can use the MCP Inspector to test the server functionalities.

  • How can I contribute to the project?

Contributions are welcome! You can submit a Pull Request on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
8enSmith
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago