wmpf-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WMPF_CDP_WS | No | Default debugger WebSocket URL. | ws://127.0.0.1:62000 |
| WMPF_ALLOW_REMOTE | No | Set to 1 to allow non-local WebSocket hosts. | |
| WMPF_CDP_TIMEOUT_MS | No | CDP connection and request timeout. | 10000 |
| WMPF_MAX_EVENT_CACHE | No | Maximum recent CDP events. | 200 |
| WMPF_MAX_SCRIPT_CACHE | No | Maximum cached script metadata entries. | 2000 |
| WMPF_MAX_NETWORK_CACHE | No | Maximum cached network entries. | 1000 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connectA | Connect to WMPFDebugger CDP WebSocket, default ws://127.0.0.1:62000. |
| statusB | Show current WMPF CDP connection status and cached debug state. |
| runtime_evaluateC | Evaluate JavaScript in the mini program runtime through CDP Runtime.evaluate. |
| cdp_callC | Call any raw Chrome DevTools Protocol method. |
| list_scriptsA | List scripts observed from Debugger.scriptParsed events. |
| get_script_sourceC | Get JavaScript source for a Debugger scriptId. |
| search_scriptsB | Search cached script sources by text or regular expression. |
| set_breakpoint_by_urlC | Set a breakpoint by URL regex and zero-based line/column. |
| set_breakpoint_by_script_idC | Set a breakpoint by CDP scriptId and zero-based line/column. |
| set_breakpoint_on_textC | Search loaded scripts and set a breakpoint at matching text/regex. Best for AI-driven debugging. |
| list_breakpointsB | List breakpoints set through this MCP session. |
| remove_breakpointC | Remove a breakpoint by CDP breakpointId. |
| paused_infoC | Show pause reason, hit breakpoints, call frames, and callFrameIds. |
| evaluate_on_callframeC | Evaluate an expression in a paused call frame to inspect local variables. |
| debugger_controlB | Control debugger execution: pause, resume, step_over, step_into, or step_out. |
| list_network_requestsC | List cached Network requests observed since connection. |
| network_capture_controlC | Start, stop, or clear CDP Network capture cache. |
| get_request_detailC | Get one network request with optional response body. |
| export_network_harC | Export cached network requests as HAR-like JSON. |
| get_response_bodyC | Get response body for a Network requestId through Network.getResponseBody. |
| last_eventsB | Show recent raw CDP events for troubleshooting protocol compatibility. |
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 21 tools
Tools are clearly distinct: breakpoint setting is split by target (text, URL, scriptId), network tools separate control from inspection, and debugging actions are compartmentalized. No overlapping purposes.
All tool names follow a consistent snake_case pattern, predominantly verb_noun or verb_preposition_noun (e.g., set_breakpoint_on_text, list_network_requests). Even single-word names like status and connect fit the overall style.
21 tools is appropriate for a debugging and inspection server covering breakpoints, scripts, network, and raw CDP. It is slightly above a typical minimal set but remains well-scoped without being excessive.
The tool surface covers core debugging and network inspection, but lacks features like conditional breakpoints, breakpoint enable/disable, watch expressions, or a disconnect tool. These gaps may require agents to work around.