NeoDB MCP Server

Connect NeoDB to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Message Control Protocol (MCP) server implementation for interacting with NeoDB. The neodb mcp server is what makes that connection.

What the server does

A Message Control Protocol (MCP) server implementation for interacting with NeoDB, a social book cataloging service. This server provides tools to fetch user information, search books, and retrieve detailed book information through NeoDB's API.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Parameters — - query (string): Search query for books

Credentials and setup notes

Configuration is passed through the environment: ACCESS_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. NeoDB's toolset — Parameters — is a fair guide to whether it matches your workflow. It is maintained by xytangme; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.