HyperspaceDB MCP Server
OfficialRelated Servers
Alternatives to HyperspaceDB MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI assistants to interact with a Qdrant vector database by exposing collection, point, vector, payload, snapshot, search, recommendation, discovery, and observability operations as MCP tools.13672 PyPI2MIT
- AlicenseAqualityBmaintenanceEnables MCP-capable agents to create and invoke OpenServerless endpoints, manage secrets, and configure integrations such as S3, PostgreSQL, Redis, Milvus, and MongoDB.13Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables agents to turn documents into vectors, perform approximate nearest neighbor search with HNSW, and filter by metadata via MCP tools for RAG workflows.MIT
- AlicenseNot gradedqualityAmaintenanceEnables LLMs to orchestrate AI agents and tasks, inspect DAG workflows, monitor cluster metrics, and perform safe database queries and statements through standardized MCP tools.189Apache 2.0
- FlicenseBqualityBmaintenanceEnables AI agents to query an air-gapped enterprise knowledge vault via seven MCP tools for deterministic and hybrid retrieval, entity graph traversal, context compression, archive inspection, onboarding scans, and node status.7-
- FlicenseNot gradedqualityDmaintenanceEnables users to ingest documents, run retrieval-augmented queries with dense/sparse search and reranking, and inspect ingestion/query traces and evaluation results through MCP tools.-
TDQS
Scored across 35 tools
Most tools are distinct, but there is direct duplication between hyperspace_query_planner and clarify_and_split_intent, which is explicitly an alias. Graph exploration tools (explore_graph, graph_traverse, get_neighbors, find_clusters) also overlap enough to cause misselection, despite descriptions helping.
Almost all tools follow a clear hyperspace_verb_noun snake_case pattern. The only notable deviation is clarify_and_split_intent, which lacks the server prefix and is an alias for another tool.
35 tools is heavy for the apparent scope, with many niche analysis, cache, and PDK extension operations. Several advanced tools feel bolted on rather than essential to the core vector-graph/memory workflow.
Coverage is broad: collections, points, text search, explicit and induced graph edges, traversal, clustering, cache, maintenance, and verification. Minor gaps exist around updating existing point content and updating collection configuration, but most workflows have a path.