mcp-ubergraph-query
Related Servers
Alternatives to mcp-ubergraph-query
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables querying and browsing ontologies from the EBI Ontology Lookup Service, including searching for terms, retrieving term details, and navigating ontology hierarchies via natural language.36 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to inspect ontology schemas, search typed objects, and execute read-only SPARQL queries against an RDF triple store.3MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLMs and AI agents to query a biomedical knowledge graph stored in RedisGraph, with tools for concept search, synonym enrichment, and study variable discovery through semantic relationships.-
- AlicenseNot gradedqualityBmaintenanceEnables querying of the Monarch Initiative biomedical knowledge graph for genes, diseases, phenotypes, and their associations through natural language or direct tool calls.46 npmMIT
- FlicenseBqualityDmaintenanceProvides reliable access to the Ontology Lookup Service (OLS) API, enabling AI assistants to accurately search and retrieve terms from biological and medical ontologies.726-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query Human Phenotype Ontology clinical phenotype terms, navigate term hierarchies, and retrieve gene-disease and disease-phenotype annotations through keyless MCP tools.16 npmMIT
TDQS
Scored across 4 tools
Each tool serves a clearly distinct purpose: searching terms, retrieving term details, getting hierarchy, and executing custom SPARQL queries. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (get_hierarchy, get_term_info, query_ubergraph, search_terms), making them predictable and easy to understand.
With 4 tools, the server is well-scoped for ontology querying. Each tool is essential and covers the primary use cases without being too few or excessive.
The tool set covers the core needs: search, term retrieval, hierarchy, and custom queries. Minimal gaps exist, such as batch operations or ontology-wide listings, but the surface is sufficient for most tasks.