SDL FAQs

Question 1

What is SDL-MCP?

Accepted Answer

SDL-MCP (Symbol Delta Ledger MCP Server) is a cards-first context system that transforms your codebase into a queryable, versioned knowledge system for AI coding agents. It indexes code into structured symbol cards and graph edges, providing precise, high-signal context.

Question 2

How does SDL-MCP help save tokens for AI agents?

Accepted Answer

SDL-MCP significantly reduces token usage by default. Instead of processing large files, agents retrieve small, structured symbol cards, build token-budgeted graph slices, and access code through policy-gated views like 'skeleton' or 'hot-path' excerpts, minimizing the need for full-file context.

Question 3

What programming languages does SDL-MCP support?

Accepted Answer

SDL-MCP offers multi-language repository indexing with Tree-sitter adapters, supporting a wide range of languages including TypeScript, JavaScript, Python, Go, Java, C#, C, C++, PHP, Rust, Kotlin, and Shell.

Question 4

What are 'symbol cards' and 'graph slices' in SDL-MCP?

Accepted Answer

Symbol cards are structured representations of code elements, detailing names, kinds, locations, signatures, summaries, dependencies, and versioning. Graph slices are task-specific, token-budgeted collections of these symbol cards and their relationships, built to provide the most relevant surrounding code for a given task.

Question 5

How does SDL-MCP ensure safe and responsible code access?

Accepted Answer

It provides a policy-gated code access ladder, allowing agents to request code in graduated options: skeleton views, hot-path excerpts, and a 'need window' for full code. Policies enforce limits, require intent signals, and enable auditing of tool calls, reducing overexposure while supporting effective debugging.

SDL

SDL

Key Features

Use Cases

Key Features

Use Cases