frida-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PID | No | Optional process ID (PID) to attach to on startup. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| attachA | Attach Frida to a process. AI MUST call this first, and MUST call it again whenever any other tool reports that the process is detached or crashed. |
| detachA | Detach Frida from the current process and unload all persistent scripts. Call this when finished with the target or before attaching to a different process. After detach you MUST call |
| load_scriptA | Load a persistent background Frida script. Use this to set up hooks that collect data over time or long-running RPC exports. Afterwards, use |
| get_script_outputA | Retrieve accumulated messages ( |
| call_rpcA | Call a function exported by a persistent script loaded via |
| unload_scriptC | Securely unload and clean up a persistent script. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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/SnowLuma/mcp-frida'
If you have feedback or need assistance with the MCP directory API, please join our Discord server