mcp-server-ladybug
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| host | No | Host to bind the MCP server for sse and stream transport mode. | 127.0.0.1 |
| port | No | Port to listen on for sse and stream transport mode. | 8000 |
| db-path | No | Path to LadybugDB database file. | :memory: |
| max-rows | No | Maximum number of rows to return from queries. | 1024 |
| max-chars | No | Maximum number of characters in query results. | 50000 |
| transport | No | Transport type. Options: stdio, sse, stream. | stdio |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| queryA | Use this to execute a Cypher query on the LadybugDB database |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| ladybugdb-initial-prompt | Core prompt for starting work with LadybugDB - emphasizes schema-first approach |
| data-types-guide | Complete reference for LadybugDB data types and complex types |
| json-guide | Guide for using JSON extension and JSON functions in LadybugDB |
| functions-guide | Reference for built-in functions: string, aggregation, date/time, type conversion |
| neo4j-differences | Key differences between LadybugDB Cypher and Neo4j Cypher |
| examples-guide | Query examples, workflows, and error handling tips |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Database Schema | Current schema of the LadybugDB database including node and relationship tables |
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined as executing Cypher queries on the LadybugDB database.
With only one tool named 'query', there is no pattern to assess consistency. However, the name is simple and descriptive, matching common conventions for a single-operation server.
A single tool is minimal for a database server. While a query tool is essential, the server likely needs additional tools for schema exploration, data manipulation, or other database operations to be functional.
The tool set is severely incomplete for typical database interactions. It only provides query execution, lacking tools for schema inspection, data definition, or other common operations, which will likely cause agent failures.