Android Proxy 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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| proxy_statusA | 获取代理服务器状态。注意：需要先在终端运行 'uv run android-proxy-start' 启动代理。 |
| get_cert_infoA | 获取 CA 证书信息和安装指南。抓取 HTTPS 流量需要在设备上安装此证书。 |
| traffic_listB | 列出捕获的 HTTP/HTTPS 流量。支持按域名、类型、状态码、URL 筛选。 |
| traffic_get_detailA | 获取单个请求的元数据（请求头、响应头、参数等）。注意：不包含请求体和响应体内容，使用 traffic_read_body 读取。 |
| traffic_searchC | 搜索流量内容。可搜索 URL、请求头、请求体、响应头、响应体。返回匹配的片段而非完整内容。 |
| traffic_read_bodyB | 分片读取请求体或响应体。用于查看大内容，支持分页读取。 |
| traffic_clearB | 清空所有捕获的流量 |
| android_list_devicesB | 列出所有连接的 Android 设备 |
| android_get_device_infoB | 获取指定 Android 设备的详细信息（型号、版本、是否 root 等） |
| android_setup_proxyA | 在 Android 设备上设置 HTTP 代理。注意：此方式对部分应用可能无效，建议在 Wi-Fi 设置中手动配置。 |
| android_clear_proxyC | 清除 Android 设备上的代理设置 |
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 11 tools
Each tool has a distinct purpose with clear boundaries: device management (list, get, clear/set proxy), certificate handling (get_cert_info), proxy server control (proxy_status), and traffic analysis (clear, list, get_detail, read_body, search). The descriptions explicitly differentiate overlapping tools like traffic_get_detail (metadata only) vs traffic_read_body (body content), preventing misselection.
Tool names follow a consistent snake_case pattern with clear prefixes: 'android_' for device operations, 'get_'/'traffic_' for certificate and traffic functions, and descriptive verb_noun combinations (e.g., traffic_list, traffic_search). No mixing of conventions or vague names, making the set predictable and readable.
11 tools are well-scoped for the server's purpose of Android proxy management and traffic analysis. The count covers device handling, proxy setup, certificate guidance, and comprehensive traffic inspection (listing, filtering, searching, reading details/bodies), with each tool earning its place without bloat or gaps.
The toolset provides complete coverage for the Android proxy domain: device discovery and info, proxy configuration (clear/set), certificate setup guidance, proxy server status, and full traffic lifecycle (capture via proxy, list, filter, search, view metadata, read bodies, clear). No obvious gaps exist; agents can perform end-to-end workflows without dead ends.