## CodeGraph MCP

Use CodeGraph for structural questions: definitions, callers, callees, impact, signatures and focused task context. Use literal search only for exact strings, comments, logs or after a specific file is already open.

| Need | Tool |
|---|---|
| Find definitions | `codegraph_search` |
| Focus an area | `codegraph_context` |
| Inspect callers | `codegraph_callers` |
| Inspect callees | `codegraph_callees` |
| Estimate impact | `codegraph_impact` |
| Read source | `codegraph_node` or `codegraph_explore` |
| Check index | `codegraph_status` |

If CodeGraph reports that the project is not initialized, ask before running `codegraph init -i`.

## SDD MCP

Use SDD MCP for read-only orchestration context. The server is configured through `.mcp.json`, `.cursor/mcp.json`, or `.claude/settings.json` and runs `sdd mcp serve --root <project-root>`.

| Need | Tool or Resource |
|---|---|
| List trace events | `sdd_trace_list` |
| Inspect a run tree | `sdd_trace_show` or `sdd://trace/{run_id}` |
| Summarize execution evidence | `sdd_trace_summary` |
| Check artifact coverage | `sdd_artifact_status` |
| Build stage context | `sdd_context_build` or `sdd://context/{orchestration}/{stage}` |
| Read complete SDD context bundle | `sdd_context_bundle` or `sdd://context-bundle/{orchestration}/{stage}` |
| Check client surfaces | `sdd_clients_doctor` |
| Check project status | `sdd_project_status` |
| Search SDD context | `sdd_search` |
| Audit quality gates | `sdd eval stage`, `sdd eval orchestration`, `sdd quality report` |

The canonical trace store remains local JSONL in `.sdd/events.jsonl`, `.sdd/subagents.jsonl`, `.sdd/task-gates.jsonl`, `.sdd/runs.jsonl`, `.sdd/evaluations.jsonl`, and `.sdd/execution-runs.jsonl`. MCP reads and exposes that state; it is not the source of truth.
