jena-mcp-server
Related Servers
Alternatives to jena-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query and modify RDF data, list named graphs, and access pre-built SPARQL templates on a Fuseki server, with optional HTTP Basic authentication.MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects AI agents to Apache Jena, enabling them to execute SPARQL queries and updates against RDF data stored in Jena Fuseki.8MIT
- AlicenseAqualityCmaintenanceMCP server exposing SPARQL query functionalities for LLMs, enabling query execution, validation, and graph exploration across SPARQL endpoints.721 PyPIMIT
- AlicenseNot gradedqualityAmaintenanceEnables LLM clients to read, search, create, edit, move, protect, and delete wiki pages, upload files, inspect revision history and recent changes, and query extension data through packs for Semantic MediaWiki, Wikibase, Cargo, Bucket, and NeoWiki. Supports multiple wikis as MCP resources with per-wiki configuration, optional OAuth-authenticated writes, stdio or HTTP transports, and paginated, size-capped responses.8 npmMIT
- FlicenseNot gradedqualityCmaintenanceExposes a DuckDB-backed MCP server that lets an agent fetch a dataset's schema and run read-only SQL queries against it. All execution is filtered server-side, enforcing single-statement, read-only safety independent of the calling model's behavior.1-
- AlicenseNot gradedqualityAmaintenanceEnables Large Language Model clients to connect to any MediaWiki-powered wiki for page reads, full-text search, revision history, file upload and download, and OAuth-authenticated edits. Supports multiple configured wikis at once, plus extension-gated tools for Semantic MediaWiki, Cargo, Wikibase, Bucket, and NeoWiki.8 npmMIT
TDQS
Scored across 16 tools
Most tools have clearly distinct purposes (e.g., load_rdf_file vs write_graph vs sparql_update), but read_graph and describe_resource overlap somewhat in retrieving graph data, and sparql_query could be used for many read operations. Descriptions help clarify boundaries, so ambiguity is minimal.
Predominantly snake_case verb_noun pattern (e.g., load_rdf_file, create_dataset, drop_graph), but a few names like dataset_stats and task_status are noun-first rather than verb-first. Still, the convention is mostly consistent and readable.
16 tools is well-scoped for a Jena/Fuseki MCP server covering dataset management, graph operations, querying, and background tasks. Each tool earns its place without redundancy.
Covers most lifecycle operations: create/delete datasets, load/write/read graphs, SPARQL query/update, backup, compact, and task status. Missing a direct tool to list all triples or export a dataset, but these can be achieved via SPARQL. Minor gaps exist but core workflows are covered.