F
licenseNot graded
qualityD
maintenanceAn MCP server that enables graph database interactions with Neo4j, allowing users to access and manipulate graph data through natural language commands.
-
@littlebigbrain/mcp
Related Servers
Alternatives to @littlebigbrain/mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server that connects AI assistants to the Data Graphs knowledge graph platform, enabling natural language search, exploration, and querying of graph data.12 npm-
- AlicenseNot gradedqualityBmaintenanceProvides a code graph querying and visualization MCP server, enabling users to search, trace, and describe code components, overlay diffs, and explore architecture through natural language.MIT
- AlicenseAqualityAmaintenanceAn MCP server for TheBrain 15 that enables semantic search, graph traversal, and structured writing to a personal knowledge base via its local API. It provides tools to read and write thoughts, notes, links, and tags, with optional local embeddings for meaning-based search.17115 npm8MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that builds a knowledge graph from code and text documents, enabling Q\&A and implementation planning via tools like graph_create, graph_plan, and graph_query.7MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables AI-powered exploration of RDF data and SPARQL querying via RDF4J. It provides tools for executing queries, searching knowledge graph resources, and retrieving schema summaries.131MIT
TDQS
A3.9/5.0
Scored across 22 tools
Disambiguation4/5
The set has a mostly clean read/manage/delete split by resource family, making most tools easy to tell apart. Some boundaries blur around lbb_evals versus lbb_models dataset actions, lbb_workflows tests, and lbb_commit versus lbb_rdf, but the descriptions generally resolve these.
Naming Consistency5/5
Names consistently use lowercase snake_case with the lbb_ prefix and resource-based suffixes such as _manage and _delete. The convention is predictable throughout, even where a write-capable tool like lbb_evals lacks the _manage suffix.
Tool Count4/5
At 22 tools the surface is somewhat heavy, but it reflects genuinely broad domains: graph reads/writes, schema, RDF, workflows, embeddings, fit sources, evals, reviews, files, and model choice. The read/manage/delete splits are purposeful rather than redundant.
Completeness4/5
Coverage is extensive across graph, ontology, workflows, evals/datasets/experiments, reviews, files, embeddings, and model management, with lifecycle operations for most resources. Minor gaps remain, such as files being read-only with no upload tool and limited dataset-item removal, but agents can largely work around them.
Maintenance
ActivityActive
ResponsivenessNo issues