nebula-mcp
Related Servers
Alternatives to nebula-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceA MCP server that exposes GraphQL schema information to LLMs like Claude. This server allows an LLM to explore and understand large GraphQL schemas through a set of specialized tools, without needing to load the whole schema into the context23 npm46MIT
- AlicenseNot gradedqualityAmaintenanceA high-performance code knowledge graph server implementing MCP, indexing codebases into a structured AST knowledge graph with semantic search, call graph traversal, and HTTP route tracing.1,612 npm77MIT
- AlicenseAqualityDmaintenanceGraphQL MCP Server that acts as a bridge allowing MCP clients (like Cursor or Claude Desktop) to interact with target GraphQL APIs through standard tools for schema introspection and operation execution.25 npm3MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for indexing source code from repositories into a Neo4j graph database and enabling Graph RAG-based search and traversal of functions via natural language queries.-
- AlicenseNot gradedqualityDmaintenanceA Node.js server that enables LLMs to inspect GraphQL schemas and retrieve information about queries, mutations, and types via MCP.15 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that exposes GraphQL operations as typed tools for AI models, with schema exploration, validation, execution, hot reload, OAuth, prompts, MCP Apps widgets, and OpenTelemetry support.7 npmMIT
TDQS
Scored across 6 tools
Each tool targets a distinct action and resource: connection testing, graph listing, GQL validation, schema retrieval, read queries, and mutations. There is no meaningful overlap, even between validate and execute, since the former never executes and the latter is read-only or mutation-specific.
All tools follow the same nebula_verb_noun pattern, with clear verbs like test, list, validate, get, and execute. The naming is consistent, predictable, and hierarchical.
Six tools is well-scoped for a graph database server covering connection, discovery, validation, schema, and execution. Each tool has a clear purpose without unnecessary bloat.
The tool surface covers the core workflow: connect, discover graphs, validate, inspect schema, execute reads, and execute mutations. Minor gaps exist, such as no explicit tool for listing all schemas or managing graphs, but these are likely outside the server's intended scope.