Skip to content

Architecture — jena-mcp

jena-mcp is a thin, layered connector: a typed REST client at the base, MCP tool

Layers

Request flow

typed tools such as jena_query, jena_get_graph or jena_create_dataset. 2. The tool wrapper resolves a JenaApi via get_client(), which reads the JENA_* environment variables, then dispatches the requested action to the matching client method. 3. JenaApi issues the corresponding Fuseki REST call — SPARQL Protocol, Graph Store Protocol, or the administration API — over requests.

Design notes

  • Single source of API surface. Every Fuseki interaction lives in jena_mcp/api/; the MCP wrappers add no business logic.
  • Action-dispatch tools. Three coarse tools (rather than dozens) keep the agent tool budget small while still covering the full protocol surface.
  • Environment-driven configuration. Connection settings come exclusively from JENA_* variables; the connector remains inactive when credentials are absent.

See Overview for the tool/endpoint matrix and Concepts for the stable concept registry.