Skip to main content
Glama
Sign In
wx-mp-mcp

wx-mp-mcp

by k98crypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Start traffic capture

mp_capture_start

Start a mitmdump proxy to record WeChat Mini Program requests as sign-crack-compatible JSONL for signature analysis. Optionally filter captured URLs by keyword; listens on port 8080 by default.

Instructions

启动 mitmdump 代理抓包。手机配置代理后，小程序请求自动记录为 sign-crack 兼容的 JSONL。默认监听 8080 端口。可选 url_filter 只抓包含指定关键词的 URL。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mp_capture_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNo代理端口 (默认 8080)
url_filterNo只捕获 URL 包含此关键词的请求

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full behavioral burden. It adds real context about the mitmdump mechanism, the default 8080 listener, and the JSONL output format, but it never says whether the call is long-running or blocking, how the running capture is terminated, or what happens if the port is already in use.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences with the core action and mechanism front-loaded, followed by setup prerequisite and the optional filter. No filler sentences, though the port default is duplicated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a long-running, side-effecting capture tool with no annotations and no output schema, the description covers purpose, setup, and output format well. It still leaves the lifecycle unspecified: whether capture runs in the background, how it stops, and how the resulting data is retrieved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented, including their defaults. The description only restates the 8080 default and the url_filter keyword behavior, adding no syntax or edge-case detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: starting an mitmdump proxy capture, and states that requests are recorded as sign-crack compatible JSONL. That distinguishes it clearly from mp_capture_stop and the read-only siblings, but it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies the prerequisite that the phone must be configured to use the proxy before capture works, which is useful setup context. However it gives no explicit when-to-use versus mp_capture_import or mp_capture_list, and no note on how capture is ended.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools