Frida MCP
A Model Context Protocol (MCP) implementation for Frida dynamic instrumentation toolkit.
Overview
This package provides an MCP-compliant server for Frida, enabling AI systems to interact with mobile and desktop applications through Frida's dynamic instrumentation capabilities. It is built on FastMCP to enable seamless integration with AI applications.
Features
- Built with FastMCP
- stdio (default), streamable HTTP, and SSE transports
- Comprehensive Frida tools exposed through MCP:
- Process management (list, attach, spawn, resume, kill)
- Device management (USB, remote devices)
- Interactive JavaScript REPL with real-time execution
- Script injection with progress tracking
- Process and device monitoring
- Resources for providing Frida data to models
- Prompts for guided Frida analysis workflows
- Progress tracking for long-running operations
- Full support for all MCP transport methods
Installation
Prerequisites
- Python 3.10 or later
- pip package manager
- Frida 16.0.0 or later
Quick Install
pip install frida-mcp-server
Development Install
# Clone the repository
git clone https://github.com/yourusername/frida-mcp.git
cd frida-mcp
# Install in development mode with extra tools
uv venv && uv pip install -e ".[dev]"
Running
# stdio (default, what MCP clients expect)
frida-mcp-server
# streamable HTTP
frida-mcp-server --transport streamable-http --host 0.0.0.0 --port 1337
# legacy SSE
frida-mcp-server --transport sse --port 1337
Client Integration
Claude Code
Add frida via the CLI:
# Stdio transport (default)
claude mcp add frida --transport stdio -- frida-mcp-server
# Or streamable HTTP transport
claude mcp add frida --transport http http://127.0.0.1:1337/mcp
Or add it directly to your configuration file (.mcp.json or ~/.claude.json):
{
"mcpServers": {
"frida": {
"command": "frida-mcp-server"
}
}
}
Codex
Add frida via the Codex CLI:
# Stdio transport (default)
codex mcp add frida -- frida-mcp-server
# Or streamable HTTP transport
codex mcp add frida --url http://127.0.0.1:1337/mcp
Or configure it in ~/.codex/config.toml (or project .codex/config.toml):
# Stdio transport
[mcp_servers.frida]
command = "frida-mcp-server"
# Or HTTP transport
# [mcp_servers.frida]
# url = "http://127.0.0.1:1337/mcp"
Crush
Add frida to your ~/.config/crush/crushrc (or .crushrc):
# Stdio transport
mcp add frida \
--command frida-mcp-server
# Or streamable HTTP transport
mcp add frida --type http \
--url "http://127.0.0.1:1337/mcp"
Or configure it in crush.json:
{
"mcp": {
"frida": {
"type": "stdio",
"command": "frida-mcp-server"
}
}
}
Usage
Once configured, you can use Frida MCP directly from your AI agent/client (Claude Code, Codex, Crush, etc.). The server provides the following capabilities:
Process Management
- List all running processes
- Attach to specific processes
- Spawn new processes
- Resume suspended processes
- Kill processes
Device Management
- List all connected devices (USB, remote)
- Get device information
- Connect to specific devices
Interactive JavaScript REPL
- Create interactive sessions with processes
- Execute JavaScript code in real-time
- Monitor process state and memory
- Hook functions and intercept calls
- Capture console.log output
- Handle errors and exceptions gracefully
Script Injection
- Inject custom JavaScript scripts
- Track injection progress
- Handle script errors and exceptions
Resources
- Get Frida version information
- Access process list in human-readable format
- Access device list in human-readable format
Development
# Clone repository
git clone https://github.com/yourusername/frida-mcp.git
cd frida-mcp
# Install development dependencies
uv venv && uv pip install -e ".[dev]"
# Run tests (frida is mocked, no device needed)
python -m pytest tests -q
License
GNU GPL v3.0
Metadata
Release files for frida-mcp-server 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| frida_mcp_server-1.0.1.tar.gz | 6.2 kB | Without provenance | Details for frida_mcp_server-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| frida_mcp_server-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for frida_mcp_server-1.0.1-py3-none-any.whl |
Total release size: 13.7 kB
Release files / frida_mcp_server-1.0.1.tar.gz
| Download URL | frida_mcp_server-1.0.1.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4875d30795ea968982d037368cd3e5aa8d46ff6ab1ffb2880715e8f3f855fa59
|
|
BLAKE2b-256 checksum How to use checksums |
5e2b0784ad642578a398428fc3ca3f1297935338b9042c9ca9bffa70aa2884cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / frida_mcp_server-1.0.1-py3-none-any.whl
| Download URL | frida_mcp_server-1.0.1-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0ad40d0c25a38039ec91219dd60307a2a45c73f92eb7d4670dc26b580424ebbe
|
|
BLAKE2b-256 checksum How to use checksums |
ab32abef501a23ab761be5170a155d8bd8ea480bca77725fd5e65d1a217ca48b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for frida-mcp-server 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.