ya-frida-mcp
Allows AI agents to dynamically instrument Android applications, manage processes, inject scripts, and interact with Frida server on Android devices via ADB.
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., "@ya-frida-mcplist connected Frida devices"
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.
WIP: Ya Frida MCP
Pending JsBridge fix #3
Existing Frida MCP servers on the market are either abandoned, poorly maintained, or limited to a handful of basic operations. ya-frida-mcp was built from scratch to be a comprehensive, production-ready bridge between AI agents and Frida — covering device management, process control, script injection, memory operations, and even ADB integration out of the box.
Features
59 MCP tools across 7 categories, all returning structured JSON for minimal token consumption.
Category | Tools | Highlights |
Device |
| Device management, system info, spawn gating, native library injection |
Process |
| Full process lifecycle; |
App |
| App enumeration with scope/identifiers filtering |
Script |
| JS injection (QJS/V8), RPC, child gating, bytecode compilation, script snapshots |
Memory |
| Read/write/scan/protect with hex I/O |
ADB (optional) |
| 17 tools, auto-registered when |
Frida Server (optional) |
| Auto-download, push, and manage frida-server on Android via ADB |
Also includes:
MCP Resources — live device list, session state, process/app enumeration as subscribable resources
MCP Prompts — workflow templates for native hooking, Java/ObjC hooking, Stalker tracing, module dumping
TOML Configuration — customize transport, default device, remote devices, timeouts
CLI Utilities —
doctor,devices,ps,ls,tools,install/uninstallfor MCP clientsOne-command client setup — register into 22+ MCP clients including Claude Desktop, Cursor, VS Code, Windsurf, Roo Code, Cline, Kiro, and more
Structured output — all tools return compact JSON with
Literaltype hints for LLM-friendly schemas
Quickstart
Install
# PyPI (recommended)
pip install ya-frida-mcp
# Or via uv
uv tool install ya-frida-mcpRegister into your MCP client
# Pick your client
ya-frida-mcp install claude-desktop
ya-frida-mcp install cursor
ya-frida-mcp install vscode
ya-frida-mcp install windsurf
ya-frida-mcp install roo-code
ya-frida-mcp install cline
# All supported clients at once
ya-frida-mcp install allKey | Client |
| Amazon Q Developer CLI |
| Augment Code |
| Claude Desktop |
| Claude Code |
| Cline |
| Copilot CLI |
| Crush |
| Cursor |
| Gemini CLI |
| Kilo Code |
| Kiro |
| LM Studio |
| Opencode |
| Qodo Gen |
| Qwen Coder |
| Roo Code |
| Trae |
| VS Code |
| VS Code Insiders |
| Warp |
| Windsurf |
| Zed |
Start the server manually
# stdio (default, used by MCP clients)
ya-frida-mcp serve
# SSE transport
ya-frida-mcp serve -t sse -H 0.0.0.0 -p 8000Configuration (optional)
ya-frida-mcp init-config # generates config.toml in current directory
ya-frida-mcp show-config # display resolved config
ya-frida-mcp -c /path/to/config.toml serve# config.toml
[server]
name = "ya-frida-mcp"
transport = "stdio" # "stdio" or "sse"
host = "127.0.0.1"
port = 8000
[frida]
default_device = "local" # "local", "usb", or device ID
script_timeout = 10
spawn_timeout = 15
[[frida.remote_devices]]
host = "192.168.1.100"
port = 27042CLI Reference
ya-frida-mcp doctor # diagnose Frida connectivity
ya-frida-mcp devices # list Frida devices
ya-frida-mcp ps # list running processes (frida-ps)
ya-frida-mcp ls # list installed apps (frida-ls)
ya-frida-mcp tools # list all registered MCP tools
ya-frida-mcp version # show version infoDevelopment
# Clone
git clone https://github.com/1shin-7/ya-frida-mcp.git
cd ya-frida-mcp
# Install dependencies
uv sync
# Run in dev mode
uv run ya-frida-mcp serve
# Lint
uv run ruff check ya_frida_mcp/
# List tools (verify registration)
uv run ya-frida-mcp toolsProject Structure
ya_frida_mcp/
├── cli.py # Click CLI entry point
├── config.py # TOML configuration management
├── installer.py # MCP client config installers
├── server.py # FastMCP server factory + lifespan
├── resources.py # MCP resources
├── prompts.py # MCP workflow prompts
├── core/
│ ├── base.py # ABC base classes + async helpers
│ ├── device.py # Frida device wrapper + manager
│ ├── session.py # Session + script lifecycle
│ ├── adb.py # ADB CLI async wrapper
│ ├── frida_server.py # frida-server download & deploy logic
│ └── output.py # Structured output helpers
└── tools/
├── device.py # Device discovery tools
├── process.py # Process management tools
├── app.py # App enumeration tools
├── script.py # Script injection + RPC tools
├── memory.py # Memory read/write/scan tools
├── adb.py # ADB CLI tools (optional)
└── frida_server.py # frida-server management tools (optional)Credits
Frida — Dynamic instrumentation toolkit
FastMCP — Pythonic MCP server framework
Click — CLI framework
Claude — AI-assisted development
License
This 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.
Latest Blog Posts
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/1shin-7/ya-frida-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server