ServiceGraph

Local-first cross-service code intelligence for AI agents

中文 · Development plan · Impact analysis plan · Integrations

ServiceGraph is building a local-first, cross-repository change intelligence engine for AI agents. It connects frontend code, gateways, backend services, contracts, configuration, registries, databases, and eventually runtime traces so a requirement or code change can become an evidence-backed impact, development, integration, and verification plan.

ServiceGraph is at the foundation stage. The CLI, configuration model, upstream detection, and MCP contracts work today. Cross-service federation is the next milestone; the diagrams below describe the target, not a finished capability.

Why ServiceGraph?

A repository code graph knows what the source says can happen. A service registry knows which service instances currently exist. A runtime trace knows what happened for one sampled request. Cross-service development needs all three views, tied to stable service, endpoint, revision, and source identities.

ServiceGraph aims to answer questions such as:

• How does a click in mall-web reach the inventory database?

• Which repository and handler implement POST /orders in the test environment?

• If this DTO, route, or service name changes, which repositories and tests are affected?

• Is this edge inferred from source, declared in a contract, or observed at runtime?

• Which services are the minimum set needed to develop this flow locally?

Related MCP server: agentmako

Architecture

flowchart LR
    CLI["CLI"] --> D["servicegraphd"]
    MCP["MCP server"] --> D
    WEB["Local Web UI<br/>(planned)"] --> D
    CBM["Codebase Memory"] --> D
    CG["CodeGraph<br/>(optional enrichment)"] --> D
    NACOS["Nacos<br/>(planned)"] --> D
    OTEL["OpenTelemetry<br/>(planned)"] --> D
    D --> GRAPH["Federated evidence graph"]
    GRAPH --> IMPACT["Impact engine<br/>(planned)"]
    IMPACT --> REPORT["Change, integration,<br/>and verification plan"]

ServiceGraph integrates with Codebase Memory as its planned default repository indexer and CodeGraph as optional in-repository enrichment. Both are independent projects and are detected as external tools; ServiceGraph does not install, bundle, or modify them.

Project status

Try the foundation

Requirements: Node.js 22+ and pnpm 11.

git clone https://github.com/LM20230311/servicegraph.git
cd servicegraph
corepack enable
pnpm install --frozen-lockfile
pnpm build

pnpm servicegraph doctor
pnpm servicegraph init /path/to/a/multi-repository-workspace
pnpm servicegraph status /path/to/a/multi-repository-workspace

Run the stdio MCP server:

pnpm mcp

The server currently registers servicegraph_explore and servicegraph_sequence. Until the federation index milestone lands, they return structured WORKSPACE_NOT_INITIALIZED or GRAPH_NOT_BUILT errors instead of inventing a flow.

Target output example

The following is an illustrative target, not output produced by the current release:

sequenceDiagram
    actor User
    participant Web as mall-web
    participant Gateway as api-gateway
    participant Order as order-service
    participant Inventory as inventory-service
    participant DB as inventory-db

    User->>Web: Submit order
    Web->>Gateway: POST /api/orders
    Gateway->>Order: POST /orders
    Order->>Inventory: POST /reservations
    Inventory->>DB: INSERT reservation
    DB-->>Inventory: reservationId
    Inventory-->>Order: reserved
    Order-->>Web: orderId

Every future arrow must carry provenance, confidence, environment, revision, and a source anchor. Static possibilities and runtime observations will never be presented as the same kind of fact.

Roadmap

1. Build the evidence-backed static vertical slice for Vue/React, Spring Cloud Gateway, controllers, OpenFeign, and JPA/MyBatis.

2. Ship Git diff impact analysis across repositories, APIs, contracts, data, and tests.

3. Add two-stage requirement anchoring and advisory PR impact reports.

4. Add Nacos, Kubernetes, and OpenTelemetry evidence plus the local Impact Workbench.

5. Generate development slices and later add permission-aware team workflows.

See the development plan for the overall roadmap and the impact analysis plan for the public model, interfaces, propagation rules, milestones, and acceptance criteria.

Contributing and security

Read CONTRIBUTING.md before proposing large API changes. Report vulnerabilities according to SECURITY.md, not in a public issue.

Independence and license

ServiceGraph is not an official extension of Codebase Memory or CodeGraph, and neither upstream project endorses or is responsible for it. See Integrations and NOTICE.

ServiceGraph is licensed under Apache-2.0.