Integrations¶

What runs alongside the agent¶

The ports worth remembering¶

3848 runs workflows and 3033 does not — sending a workflow to the health API returns a confusing 404, and it is the single most common mix-up here.

Check they are up¶

coding --health         # every service at once
curl -s localhost:3033/health | jq .

The services¶

Everything below runs as a container and is started for you by coding.

Semantic Analysis hosts the multi-agent knowledge workflows — the extraction pass that builds the knowledge graph, plus ontology management and entity refresh. It speaks HTTP/SSE on 3848, which is also what feeds the dashboard's live workflow view. Reach it with the semantic CLI rather than by hand.

Constraint Monitor evaluates rules against tool calls and records what fired. Its dashboard is on 3030, its API on 3031. The constraints CLI works even when the container is down, because it runs the check in-process.

Graphify builds a static tree-sitter graph of the codebase and serves it over MCP on 3851. It answers structural questions — what calls this, where is that defined — without a database and without guessing. Rebuild it when it goes stale; it is a snapshot, not a live index.

The dashboard on 3032 is the single front-end for health, token usage, routing, measurement and benchmarks. The health API behind it is on 3033.

The LLM CLI proxy on 12435 is the one path every LLM call takes, which is what makes routing, fallback and token accounting possible at all. Its endpoint is POST /api/complete — not the OpenAI-shaped /v1/chat/completions.

Ports¶

Two pairs are easy to confuse and worth committing to memory: 3848 runs workflows, 3033 reports health; and 12435 is the proxy, 12436 is observations. Both mistakes fail as a 404 rather than an error that names the problem.

Configuration¶

MCP servers are declared in the agent's own MCP configuration, pointing at the containerised endpoints through stdio proxies. The containers are brought up by coding, so in normal use there is nothing to start by hand — if a tool is missing from the agent, check the container is running before suspecting the config.

When something is not answering¶

coding --health                                  # the summary
docker compose -f docker/docker-compose.yml ps   # which containers are actually up
curl -s localhost:3033/health | jq .             # what the API believes

A service that is up but not answering its health check is usually mid-restart; one that is absent from docker ps never started, which is a Docker problem rather than a coding one.

MCP servers and tools that extend the coding infrastructure.

MCP Servers¶

Service Ports¶

Architecture¶

flowchart TB
    CC[Claude Code] --> MCP{MCP Protocol}
    MCP --> SA[Semantic Analysis]
    MCP --> CM[Constraint Monitor]
    MCP --> CGR[Graphify]

    SA --> GDB[(GraphDB)]
    SA --> QD[(Qdrant)]
    CGR --> GJ[graph.json]
    CM --> CMDB[(Violations DB)]

    GDB --> VKB[VKB Dashboard]
    CMDB --> CMD[Constraint Dashboard]

MCP Configuration¶

MCP servers are configured automatically by the installer. They run as HTTP/SSE services in Docker containers; Claude communicates via stdio-proxy:

Claude Code <-> stdio-proxy.js <-> HTTP/SSE <-> Docker Container

Configuration Location¶

• macOS/Linux: ~/.claude/settings.json
• Windows: %APPDATA%/Claude/settings.json

Available Tools¶

Each MCP server provides tools accessible within Claude sessions:

Semantic Analysis Tools¶

Constraint Monitor Tools¶

Graphify Tools¶

Health Checks¶

# Check all health endpoints
for port in 3848 3849 8080 3032; do
  echo "Port $port: $(curl -s http://localhost:$port/health | jq -r '.status // "N/A"')"
done

# Check MCP servers are registered
cat ~/.claude/settings.json | jq '.mcpServers | keys'

Submodule Management¶

Integration components are git submodules:

# Update all submodules
git submodule update --remote

# Initialize missing submodules
git submodule update --init --recursive

# Update specific submodule
git submodule update --remote integrations/semantic-analysis

Related Documentation¶

• Configuration - API keys and settings
• Data Flow - Integration data flow