Dolphin DAP 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dolphin_startC | Start Dolphin with an ELF, optional disc and source roots, then connect its DAP server. |
| dolphin_connectC | Connect and initialize an existing Dolphin DAP server. |
| dolphin_disconnectC | Disconnect DAP and optionally terminate a Dolphin process started by this server. |
| dolphin_statusA | Show DAP connection state, capabilities, queued events, and managed Dolphin PID. |
| dolphin_requestC | Send any standard or Dolphin-specific DAP request. This is the complete protocol escape hatch. |
| dolphin_eventsC | Drain queued asynchronous DAP events, or wait for one named event. |
| dolphin_executionC | Pause, continue, step, restart, terminate, or inspect Dolphin's PPC execution state. |
| dolphin_breakpointsC | Replace source, instruction, or data breakpoints using native DAP argument shapes. |
| dolphin_stackC | Get the PPC call stack with DWARF source paths and lines when available. |
| dolphin_variablesC | Inspect scopes/variables, set a register, or evaluate a PPC debugger expression. |
| dolphin_memoryC | Read or write emulated memory. Reads return both base64 and hexadecimal data. |
| dolphin_disassembleC | Disassemble PPC instructions around an emulated address. |
| dolphin_sourcesC | List loaded sources, fetch source text, or query valid breakpoint lines. |
| dolphin_watchC | Create/cancel realtime watches or freeze/unfreeze emulated memory. |
| dolphin_scanC | Start, refine, inspect, cancel, dispose, undo, or filter a Dolphin memory scan. |
| dolphin_codeC | Find free memory, inject raw PPC code, create a detour, or resolve a pointer chain. |
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 16 tools
Each tool targets a distinct debugging domain such as connection lifecycle, execution control, breakpoints, stack/variables, memory, scanning, and code injection. The only broadly overlapping tool is dolphin_request, but it is explicitly documented as a protocol escape hatch, so it does not create misselection among dedicated tools.
All tools share the dolphin_ snake_case prefix, which keeps them readable and grouped. The set mixes action verbs (start, connect, disconnect) with domain nouns (execution, breakpoints, memory), so it is not a pure verb_noun convention but remains mostly consistent.
16 tools is slightly above the typical 3–15 range, but the server covers a complex DAP/emulator debugging surface with distinct capabilities. Each tool appears justified by a separate domain such as execution, memory, scan, or code injection, so the count is reasonable.
The toolset provides lifecycle management (start/connect/disconnect), execution control, breakpoints, stack/variables, memory access, disassembly, sources, watches, memory scanning, and code injection. The dolphin_request escape hatch further ensures any standard or Dolphin-specific DAP request is reachable, leaving no obvious dead ends.