Work from the symbols that matter
SDL-MCP indexes a repository into a symbol graph and gives coding agents a controlled path from compact metadata to source code. Instead of starting with full files, an agent can search symbols, inspect cards, build a task-scoped slice, and request a bounded code window only when it needs one.
The result is a smaller, more deliberate context surface for debugging, reviews, implementation work, and repository exploration. SDL-MCP runs locally and supports the Model Context Protocol over stdio or HTTP.
Start in a few minutes
SDL-MCP requires Node.js 24 or later. For an interactive first install, run the wrapper package from the repository you want to index:
npx create-sdl-mcp
For a standard global install, initialize the repository, verify it, then start the stdio server:
npm install -g sdl-mcp
cd <repository>
sdl-mcp init
sdl-mcp doctor
sdl-mcp serve --stdio
Use sdl-mcp init -y --auto-index for non-interactive setup. The Getting Started guide covers the setup wizard, supported clients, HTTP transport, and configuration examples.
A controlled retrieval loop
- Index the repository into symbols, relationships, and compact metadata.
- Start with symbol search, task-shaped context, or graph slicing.
- Escalate through progressively richer views only when the task requires more detail.
The Iris Gate Ladder makes the escalation explicit. Cards, skeletons, hot paths, and policy-gated source windows let an agent ask for the least code that can answer its question.
The generated tool inventory is the source of truth for registered tools and mode counts.
| Mode |
Registered surface |
| Flat |
38 tools: 2 universal tools and 36 flat tools |
| Gateway |
6 tools: 2 universal tools and 4 gateway namespaces |
| Gateway with legacy |
42 tools: 2 universal, 4 gateway, and 36 flat tools |
| Code Mode exclusive |
7 tools: sdl.action.search, sdl.context, sdl.file, sdl.info, sdl.manual, sdl.retrieve, and sdl.workflow |
Code Mode provides a compact task-oriented surface. Gateway mode groups the regular actions into sdl.agent, sdl.code, sdl.query, and sdl.repo. The MCP Tools Reference explains requests and responses for the installed surface.
Build context from repository structure
Symbol cards
Each indexed symbol has a compact card with its identity, signature, summary, relationships, and other retrieval metadata. Cards give an agent a place to begin without opening a full source file.
Graph slicing
Graph slicing follows repository relationships rather than directory boundaries. Give SDL-MCP a task or a starting symbol and it returns a budgeted subgraph that can be refreshed or expanded through spillover.
Read about graph slicing · Read about task-shaped context
Understand change and work against current code
Delta packs and blast radius
SDL-MCP can compare indexed versions, identify changed symbols, and trace affected relationships. sdl.pr.risk.analyze packages change evidence and test recommendations for pull-request review.
Live indexing
Draft-buffer updates can appear in a live overlay before the underlying file is saved. An accepted save then queues targeted reconciliation; configured SCIP, LSP, or parser preparation runs in the background and publishes only the latest saved generation. Retrieval continues from the committed graph and, when present, the overlay while that work prepares.
Read about delta packs · Read about live indexing
Use compiler and provider facts when they are available
SDL-MCP uses tree-sitter for repository structure and can ingest SCIP and language-provider facts through provider-first indexing. This adds precise cross-references where a provider covers the file and falls back to the regular path for files it does not cover.
Read about SCIP integration · Read about provider-first indexing
Keep useful knowledge with the work
Development memories are opt-in. When enabled, they store decisions and task notes with repository links so later work can retrieve them alongside the relevant context. Memory behavior and storage rules are documented in the Memory Protocol.
Gateway mode reduces the visible regular action surface to four namespace tools while preserving server-side validation and routing. Use it when a client benefits from fewer tool choices; use the flat surface when direct tool names are more useful.
Read about the Tool Gateway · Read about Code Mode
Operate the repository with guardrails
Policy settings govern raw source windows. The runtime execution surface also applies configured executable, working-directory, environment, concurrency, and timeout controls. For HTTP deployments, SDL-MCP includes the graph viewer and observability dashboard.
Governance and policy · Runtime execution · Graph viewer · Observability dashboard
Documentation map
License
SDL-MCP is source-available. The Community License permits use, running, and modification, including internal business use. A commercial license is required before selling, licensing, sublicensing, bundling, embedding, or distributing SDL-MCP as part of a monetized product.
评论