Architecture Intelligence Platform MCP server

Architecture Intelligence Platform

Agents should reason about architecture — not reconstruct it.

AIP gives coding agents evidence-qualified architecture context.

It reconciles declared API contracts with observed runtime behavior so an agent can distinguish:

• dependencies that are declared and observed;
• dependencies seen in production but documented nowhere;
• declared relationships not observed in the selected runtime window;
• facts AIP cannot safely establish.

Every answer is snapshot-bound and traceable to evidence. The agent-facing tools are read-only. Four real coding-agent clients were qualified end to end against v0.4.2 — see the v0.4.2 compatibility matrix. That qualification has not been repeated since.

Run the 5-Minute Demo · Realistic Demo: Quarkus Super Heroes · MCP Tools · How It Works

MCP Registry: io.github.michaelegner/architecture-intelligence-platform

LegacyPricingService was never declared. AIP observed the dependency at runtime as OBSERVEDONLY and traces the claim back to its OpenTelemetry evidence.**

⭐ Star AIP if evidence-qualified architecture context for coding agents is a problem you want solved.

Video Walkthrough · Evaluation · Boundaries · Documentation · Research Landscape

See It in Five Minutes

Requires Docker (with Compose), curl and jq. No LLM API key — nothing on this path calls a model:

git clone https://github.com/michaelegner/architecture-intelligence-platform.git
cd architecture-intelligence-platform
cp .env.example .env
examples/runtime-demo/mcp-demo.sh

The script starts AIP + Neo4j + an OTel Collector, imports the bundled example architecture, seeds one timestamp-frozen batch of runtime telemetry, then drives tools/list → getarchitecturedrift → get_evidence over plain HTTP/JSON-RPC — the same direct 2026-07-28 request path a compatible MCP client would take.

Asking getarchitecturedrift about order-service returns two findings:

ProductService and PaymentService (via payment-q) are CONFIRMED — declared and observed — and correctly don't appear at all: drift returns discrepancies, never matches. getservicedependencies is the tool that lists all four. Alongside the two claims the answer carries a limitations entry: AIP declining to name a consumer for unused-q that it cannot evidence. Each claim's evidencerefs then resolve through getevidence, at the same snapshot_id, to the asyncapi.yaml that declared one and the OpenTelemetry window that observed the other.

The full JSON both calls return

Shortened. The full README is on GitHub.