Skip to main content
Glama
keonchennl

GraphDB MCP Server

by keonchennl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to GraphDB MCP Server

No user-submitted related servers found.

    Related Servers

    • Ontology MCP

      bigdata-coss
      A
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that connects GraphDB's SPARQL endpoints and Ollama models to Claude, enabling Claude to query and manipulate ontology data while leveraging various AI models.
      28
      3
      MIT

    • RDF Explorer

      emekaokoye
      A
      license
      Not graded
      quality
      F
      maintenance
      The Model Context Protocol (MCP) server provides a conversational interface for the exploration and analysis of RDF Turtle Knowledge Graph in Local File mode or SPARQL Endpoint.
      54
      MIT
    • Memgraph MCP Server by memgraph

      Memgraph MCP Serverofficial

      memgraph
      A
      license
      C
      quality
      Not graded
      maintenance
      A lightweight server implementation of the Model Context Protocol that connects Memgraph database with LLMs, allowing users to interact with graph databases through natural language.
      1
      25
      MIT

    • 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

    • RDF4J MCP Server

      odysa
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI-powered exploration of RDF data and SPARQL querying via RDF4J. It provides tools for executing queries, searching knowledge graph resources, and retrieving schema summaries.
      13
      1
      MIT
    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

    B3.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one lists available graphs, while the other executes queries against them. There is no overlap in functionality, making it impossible to confuse their intended use.

    Naming Consistency4/5

    Both tools use camelCase naming, which is consistent, but they follow different patterns: 'listGraphs' uses a verb-noun structure, while 'sparqlQuery' uses a noun-verb structure. This minor deviation prevents a perfect score.

    Tool Count2/5

    With only two tools, the server feels thin for a GraphDB domain, lacking essential operations like creating, updating, or deleting graphs or data. This minimal set is insufficient for typical database workflows.

    Completeness2/5

    The server covers listing and querying but misses critical CRUD operations for a GraphDB system, such as creating graphs, inserting data, or modifying content. This creates significant gaps that will hinder agent tasks.

    Maintenance

    ActivityNo data
    ResponsivenessResponsive

    Resources