SPARQL MCP
Related Servers
Alternatives to SPARQL MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables users to write and execute SPARQL queries against open-access SPARQL endpoints by providing relevant query examples, schema information, and endpoint metadata. Supports querying biological databases like UniProt and Bgee through natural language interactions.12MIT
- AlicenseAqualityCmaintenanceMCP server exposing SPARQL query functionalities for LLMs, enabling query execution, validation, and graph exploration across SPARQL endpoints.779 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query the WikiPathways open community pathway database via natural language, part of the Pipeworx MCP gateway.126 npmMIT
- AlicenseNot gradedqualityBmaintenanceA unified biomedical graph database that integrates 50+ primary data sources — genes, proteins, compounds, diseases, pathways, and clinical data — into a single queryable graph with billions of cross-reference edges. Its native MCP server gives LLMs direct access to structured, authoritative biomedical data, complementing their reasoning with reliable identifiers and up-to-date database content.20AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables agents to resolve named entities, retrieve curated Wikidata triples, discover cross-links and inbound relations, and run guarded SPARQL queries against a local Truthy knowledge graph for executive brief enrichment.12 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables LLMs and AI agents to search a biomedical knowledge graph for concepts and study variables, traverse semantic relationships, and look up BioData Catalyst PIC-SURE paths for cohort building.-
TDQS
Scored across 5 tools
Each tool occupies a distinct slot in a clear workflow: schema orientation (get_schema_card), entity IRI resolution (resolve_entity), execution (run_sparql), and example discovery/retrieval (search_examples vs get_example). The search/fetch pair is a well-understood pattern with non-overlapping roles. No tool can plausibly be mistaken for another.
All five names follow the same lower_snake_case verb_noun pattern: get_schema_card, resolve_entity, run_sparql, search_examples, get_example. The verbs are accurate and consistent (get_ for retrieval, search_ for discovery, run_ for execution). No style mixing.
Five tightly scoped tools for a read-only SPARQL endpoint is right-sized; each one maps to a real step an agent must take (orient, resolve IRIs, query, find examples). Nothing feels padded or absent for the stated scope.
The surface covers the full query lifecycle: schema discovery, entity resolution, example search/fetch, and execution with self-repairing error feedback. Minor gaps remain — no result pagination/continuation beyond the 1000-row ceiling and no standalone prefix or graph-listing helper (both only indirectly available via the schema card) — but agents can work around these with SPARQL itself.