hostproto-dap-delve
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@hostproto-dap-delvedebug my Go program and show goroutines"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
hostproto-dap-delve
The second HostProto DAP adapter: a Delve (dlv dap, Go) session
exposed through MCP 2026-07-28, pinned to the same eleven
hostproto-semantics
bundles as hostproto-dap-debugpy
and hostproto-mcp-playwright.
It exists to test kill gate 1 late: does a second, unrelated debugger need a
different envelope? It did not. The diff against the debugpy adapter was the
measurement (docs/DECISIONS.md ADR-0001), and that diff is now
src/binding.ts: since hostproto-semantics ADR-0012 both adapters are
bindings on hostproto-dap-core.
What differs from debugpy, and where it went
Delve fact | Where it landed |
| the core's |
|
|
debuggee stdio rides | normalized into the same |
goroutines are threads; | every surface is stamped with the event's reason and the thread that caused it |
| the spike's "verified only the bound one" case is reachable here (debugpy relocates instead) |
no reverse requests |
|
|
|
Everything else — handles, revision per thread, host-assigned cursor,
revision-scoped targets refused before send, preconditions, receipts with
unknown, omitted-not-lost, recovery with the DAP log as evidence, the
earned capability profile — is the debugpy adapter's code, unchanged.
Related MCP server: DebugPilot
Run
npm ci
go install github.com/go-delve/delve/cmd/dlv@v1.27.1 # or HOSTPROTO_DLV=/path/to/dlv
npm test # real client ↔ real server over stdio ↔ real dlv dap ↔ real Go program
npm startThis server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to perform interactive Python debugging with breakpoints, step execution, and variable inspection using the Debug Adapter Protocol (DAP) through an MCP server interface.81MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to inspect debug state, control execution, and set breakpoints in VS Code by exposing the Debug Adapter Protocol as an MCP server.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides Claude with direct debugging capabilities via the Debug Adapter Protocol, currently supporting Go debugging with dlv dap.171MIT
- AlicenseNot gradedqualityBmaintenanceExposes VS Code's Debug Adapter Protocol as MCP tools, enabling AI coding agents to set breakpoints, step through code, inspect variables, and read exceptions in a real debug session.GPL 3.0
Related MCP Connectors
A MCP server built for developers enabling Git based project management with project and personal…
MCP server for interacting with the Supabase platform
Workflow diagnostics, capability routing, and x402 settlement for MCP-compatible agents.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/bayleafwalker/hostproto-dap-delve'
If you have feedback or need assistance with the MCP directory API, please join our Discord server