Skip to content

Deployment

Deployment Options

jena-mcp supports local stdio, a loopback-only development listener, a least-privilege stdio container, and a remote authenticated HTTPS boundary. Provider endpoint, credential, selector, identity, and trust material are supplied at runtime through AgentConfig; none is stored in this repository.

Installed stdio process

{
  "mcpServers": {
    "jena": {
      "command": "jena-mcp",
      "args": [],
      "env": {"MCP_TOOL_MODE": "intent"}
    }
  }
}

Loopback development listener

jena-mcp --transport streamable-http --host 127.0.0.1 --port 8000

Do not expose this listener beyond loopback. Network deployments require direct TLS or an explicitly trusted TLS-terminating ingress, configured authentication, exact MCP_ALLOWED_HOSTS, and an exact trusted-proxy CIDR policy.

Least-privilege local container

docker run -i --rm \
  --read-only \
  --cap-drop=ALL \
  --security-opt=no-new-privileges \
  --pids-limit=256 \
  --tmpfs /tmp:rw,noexec,nosuid,nodev,size=64m \
  -e TRANSPORT=stdio \
  registry.example.invalid/jena-mcp@sha256:<digest> jena-mcp

The operator projects the selected AgentConfig profile into the process at runtime; the image remains immutable and contains no environment connection profile.

Remote authenticated HTTPS endpoint

{
  "mcpServers": {
    "jena": {"url": "https://service.example.invalid/mcp"}
  }
}

Store the real remote URL, outbound identity reference, and TLS-profile reference in AgentConfig, not in MCP client JSON or documentation.

This page covers running jena-mcp as a long-lived server: the transports, a Docker Compose stack, putting it behind a Caddy reverse proxy, and giving it a DNS name with Technitium. To provision the Apache Jena Fuseki server it connects to, see Backing Platform.

Run the MCP server

The transport is selected with --transport (or the TRANSPORT env var):

jena-mcp
For IDE / desktop MCP clients that start the server as a subprocess.

jena-mcp --transport streamable-http --host 0.0.0.0 --port 8000
A network server with a /health endpoint and /mcp route.

jena-mcp --transport sse --host 0.0.0.0 --port 8000

Health check (HTTP transports):

curl -s http://localhost:8000/health        # {"status":"OK"}

Configuration (environment)

jena-mcp is configured entirely from the environment. The required set:

Var Default Meaning
JENA_FUSEKI_URL http://localhost:3030 Fuseki server base URL (alias: JENA_URL)
JENA_USERNAME (unset) Basic-auth user id
JENA_PASSWORD (unset) Basic-auth password
JENA_TOKEN (unset) Bearer token (used in place of basic auth)
JENA_TLS_PROFILE system Named outbound TLS policy from AgentConfig
JENATOOL True Register the Jena tool set

Plus HOST / PORT / TRANSPORT for HTTP transports. A starting template is provided in .env.example — copy it to .env and fill in the operator's connection settings.

Docker Compose

The repo ships docker/mcp.compose.yml. The following stack reads a sibling .env and publishes the HTTP server on :8000:

services:
  jena-mcp:
    image: example/jena-mcp@sha256:<digest>
    container_name: jena-mcp
    hostname: jena-mcp
    restart: always
    env_file:
      - .env
    environment:
      - PYTHONUNBUFFERED=1
      - HOST=0.0.0.0
      - PORT=8000
      - TRANSPORT=streamable-http
    ports:
      - "8000:8000"
    healthcheck:
      test: ["CMD", "python3", "-c", "import urllib.request; urllib.request.urlopen('http://localhost:8000/health')"]
      interval: 30s
      timeout: 10s
      retries: 3
cp .env.example .env          # then edit JENA_* values
docker compose -f docker/mcp.compose.yml up -d
docker compose -f docker/mcp.compose.yml logs -f

Behind a Caddy reverse proxy

Expose the HTTP server on a hostname with automatic TLS. Add to the operator's Caddyfile:

# Internal (self-signed) — homelab .example.invalid zone
jena-mcp.example.invalid {
    tls internal
    reverse_proxy jena-mcp:8000
}
# Public — automatic Let's Encrypt
jena-mcp.example.com {
    reverse_proxy jena-mcp:8000
}

Reload Caddy:

docker compose -f services/caddy/compose.yml exec caddy caddy reload --config /etc/caddy/Caddyfile

DNS with Technitium

Point the hostname at the host running Caddy. Via the Technitium API:

curl -s "http://technitium.example.invalid:5380/api/zones/records/add" \
  --data-urlencode "token=$TECHNITIUM_DNS_TOKEN" \
  --data-urlencode "domain=jena-mcp.example.invalid" \
  --data-urlencode "zone=arpa" \
  --data-urlencode "type=A" \
  --data-urlencode "ipAddress=192.0.2.10" \
  --data-urlencode "ttl=3600"

…or add an A record jena-mcp.example.invalid → <caddy-host-ip> in the Technitium web console (http://technitium.example.invalid:5380). The ecosystem technitium-dns-mcp automates this as a tool.

Register with an MCP client

Add to the operator's client's mcp_config.json:

{
  "mcpServers": {
    "jena-mcp": {
      "command": "uv",
      "args": ["run", "jena-mcp"],
      "env": {
        "JENA_FUSEKI_URL": "http://your-fuseki:3030",
        "JENA_USERNAME": "admin",
        "JENA_PASSWORD": "admin",
        "JENA_TLS_PROFILE": "system",
        "SSL_CERT_FILE": "/run/secrets/private-ca-bundle.pem",
        "JENATOOL": "True"
      }
    }
  }
}

For a remote HTTP server, point the client at http://jena-mcp.example.invalid/mcp instead.

Point the agent at a running MCP server and serve it on :8001

The repo ships
to run the agent alongside the MCP server:

```yaml
services:
    image: example/jena-mcp@sha256:<digest>
    container_name: jena-agent
    hostname: jena-agent
    restart: always
    command: ["jena-agent", "--host", "0.0.0.0", "--port", "8001"]
    env_file:
      - .env
    environment:
      - PYTHONUNBUFFERED=1
      - MCP_URL=http://jena-mcp:8000/mcp
    ports:
      - "8001:8001"
    depends_on:
      - jena-mcp

```bash