Delve MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Server capabilities have not been inspected yet.
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 |
| setBreakpointC | 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 |
| stepoutC | Step out of current function |
| variablesC | List local variables in current scope |
| evaluateC | Evaluate an expression in current scope |
| coreC | 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 | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dwisiswant0/delve-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server