Delve MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| debugC | Start debugging a Go package |
| attachC | Attach to a running process |
| execC | Debug a precompiled binary |
| testC | Debug tests in a package |
| setBreakpointB | Set a breakpoint in the debugged program |
| removeBreakpointC | Remove a breakpoint |
| continueC | Continue program execution |
| nextC | Step over to next line |
| stepC | Step into function call |
| stepoutB | Step out of current function |
| variablesC | List local variables in current scope |
| evaluateC | Evaluate an expression in current scope |
| coreB | Examine a core dump |
| dapC | Start a DAP (Debug Adapter Protocol) server |
| replayC | Replay an rr trace |
| traceC | Trace program execution |
| versionB | Get Delve version information |
| setBackendC | Set the backend for debugging |
| configureLoggingC | Configure debug logging |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Tools have distinct purposes with clear descriptions. Some potential confusion exists between 'debug', 'exec', 'test', and 'attach' as different ways to start debugging, but descriptions differentiate them. Overall, agents can reliably distinguish tools.
All tools use a consistent single-word lowercase naming pattern (e.g., 'continue', 'step', 'setBreakpoint'). While not verb_noun, the pattern is uniform and predictable, making it easy for agents to understand.
19 tools is on the higher end for a debugger MCP server. While each tool serves a legitimate debugging function, the count exceeds the typical 3-15 range, making it somewhat heavy but still manageable.
Covers core debugging workflows like starting, stepping, breakpoints, and evaluation. However, missing common operations like listing breakpoints, viewing stack traces, and goroutine inspection indicate notable gaps for comprehensive debugging.