NeoDB MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_BASE | Yes | The base URL for the NeoDB API | |
| ACCESS_TOKEN | Yes | Your NeoDB API access token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-user-infoB | Get current user's basic info |
| search-booksC | Search items in catalog |
| get-bookC | Get detailed information about a specific book |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get-book retrieves details for a specific book, get-user-info fetches user information, and search-books performs catalog searches. There is no overlap in functionality, making tool selection straightforward for an agent.
The naming follows a consistent verb_noun pattern with hyphens (e.g., get-book, get-user-info, search-books), which is predictable and readable. The minor deviation is that get-user-info uses 'info' instead of a more specific noun like 'user', but overall the pattern is well-maintained.
With only 3 tools, the set feels thin for a database server, potentially lacking operations like create, update, or delete for books or users. While the tools cover basic retrieval and search, the scope suggests more comprehensive functionality might be expected.
The tool surface is significantly incomplete for a database server, as it only provides read operations (get and search) with no ability to modify data (e.g., create, update, delete books or users). This creates gaps that could lead to agent failures when full CRUD operations are needed.