NeoDB MCP Server

Created By
xytangmea year ago
A Message Control Protocol (MCP) server implementation for interacting with [NeoDB](
Overview

What is NeoDB MCP Server?

NeoDB MCP Server is an implementation of the Message Control Protocol (MCP) designed for interacting with NeoDB, a social book cataloging service. It provides tools to fetch user information, search for books, and retrieve detailed book information through NeoDB's API.

How to use NeoDB MCP Server?

To use the NeoDB MCP Server, you need to set it up by installing the UV package installer, creating a virtual environment, and installing the necessary dependencies. After setup, you can interact with the server using various tools provided.

Key features of NeoDB MCP Server?

  • Fetch current user's basic information with the get-user-info tool.
  • Search for books in the catalog using the search-books tool.
  • Retrieve detailed information about specific books with the get-book tool.

Use cases of NeoDB MCP Server?

  1. Users can obtain their profile information from NeoDB.
  2. Developers can integrate book search functionality into their applications.
  3. Researchers can analyze book data from the NeoDB catalog.

FAQ from NeoDB MCP Server?

  • How do I get my access token?

You can obtain your access token by following the official documentation or using the automated script provided in the repository.

  • What programming language is used for this project?

The NeoDB MCP Server is implemented in Python.

  • Is there a license for this project?

Yes, this project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
xytangme
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