Skip to main content
Glama
MatthiasVanDE

jena-mcp-server

by MatthiasVanDE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to jena-mcp-server

No user-submitted related servers found.

    Related Servers

    • MCP Server for Apache Jena

      ramuzes
      A
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      8
      MIT

    • mcp-sparql

      daedalus
      A
      license
      A
      quality
      C
      maintenance
      MCP server exposing SPARQL query functionalities for LLMs, enabling query execution, validation, and graph exploration across SPARQL endpoints.
      7
      MIT

    • sql_tool

      ShadowOO7
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes 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.
      -

    • GraphDB MCP Server

      keonchennl
      A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol server that provides read-only access to Ontotext GraphDB, enabling LLMs to explore RDF graphs and execute SPARQL queries.
      2
      11 npm
      16
      GPL 3.0

    • Artsdata MCP Server

      culturecreates
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables clients to search and retrieve Artsdata entities in English or French, run SPARQL queries against the Artsdata endpoint, fetch the compiled Artsdata schema, and discover the download URL and version of the latest core-minus-provenance dump via the Databus. It exposes these capabilities as MCP-style tools and resources over HTTP, with configurable endpoints, timeouts, row limits, and CORS.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 16 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources