Labsco
MCP SERVER

GraphDB

by keonchennl ↗

Run read-only SPARQL against a GraphDB repository and list the named graphs it holds, in a response format you choose.

NoSQL, Graph & Key-Value Stores✓ Verified
Summary
Query access to a knowledge graph without an update path

sparqlQuery is declared read-only, so a model exploring an unfamiliar graph cannot rewrite it with a mis-generated statement — the risk of handing a triple store to an assistant drops to wasted tokens. listGraphs supplies the graph names the query tool expects, which makes it the usual first call. Neither tool takes a connection parameter, so which repository you reach is settled by the server's configuration rather than per call.

What it is

A GraphDB client with two tools: a read-only SPARQL query scoped to a graph, and a listing of the repository's graphs.

What you get
  • SPARQL execution against the repository, declared read-only, with a target graph and an output format you specify
  • The names of every graph the repository holds, which is what the query tool's graph parameter expects
Requirements

A GraphDB repository the server can reach, and GPL-3.0 terms if you redistribute it.

Setup effort

One command plus a key — npx -y mcp-server-graphdb, then supply credentials