Skip to main content
Glama
rmorgans

Frida MCP

by rmorgans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FRIDA_DEFAULT_DEVICENoEnvironment variable for setting the default Frida device
FRIDA_DEFAULT_REMOTENoEnvironment variable for setting the default remote Frida endpoint
FRIDA_DEVICE_FALLBACKSNoEnvironment variable for controlling automatic device discovery fallback order

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
enumerate_processesA

List all processes running on the system.

Returns:
    A list of process information dictionaries containing:
    - pid: Process ID
    - name: Process name
enumerate_devicesA

List all devices connected to the system.

Returns:
    A list of device information dictionaries containing:
    - id: Device ID
    - name: Device name
    - type: Device type
    - hint: How to reference the device via device_id
    - alias: Configured alias for remote devices (if any)
    - default_candidate: Whether the device is the current default choice
configure_remote_deviceB

Connect to a remote Frida server and make it available for future requests.

get_deviceC

Get a device by its ID.

Returns:
    Information about the device
get_usb_deviceC

Get the USB device connected to the system.

Returns:
    Information about the USB device
get_local_deviceC

Get the local device.

Returns:
    Information about the local device
get_process_by_nameC

Find a process by name.

attach_to_processC

Attach to a process by ID.

spawn_processC

Spawn a program.

Returns:
    Information about the spawned process
resume_processC

Resume a process by ID.

Returns:
    Status information
kill_processC

Kill a process by ID.

Returns:
    Status information
create_interactive_sessionB

Create an interactive REPL-like session with a process.

This returns a session ID that can be used with execute_in_session to run commands.

Returns:
    Information about the created session
execute_in_sessionA

Execute JavaScript code within an existing interactive Frida session.

This tool allows for dynamic scripting against a process previously attached to
via `create_interactive_session`.
get_session_messagesA

Retrieve and clear messages sent by persistent scripts in a session.

Returns:
    A list of messages captured since the last call, or an error if the session is not found.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
get_versionGet the Frida version.
get_processes_resourceGet a list of processes from the currently selected default device as a readable string.
get_devices_resourceGet a list of all devices as a readable string.
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 14 tools

Disambiguation4/5

Most tools have distinct purposes, but some potential overlap exists between 'attach_to_process' and 'create_interactive_session' (both involve attaching to processes), and between 'get_device', 'get_local_device', and 'get_usb_device' (all retrieve device information). The descriptions help clarify differences, but an agent might initially confuse these pairs.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern with clear verb_noun structures (e.g., 'enumerate_processes', 'get_session_messages', 'spawn_process'). There are no deviations in naming conventions, making the set predictable and readable.

Tool Count5/5

With 14 tools, this server is well-scoped for Frida's dynamic instrumentation domain. The count covers essential operations like device management, process control, and session handling without being excessive, ensuring each tool has a clear role.

Completeness4/5

The tool set provides strong coverage for Frida's core workflows, including device enumeration, process management, and interactive scripting. A minor gap is the lack of tools for detaching from processes or terminating sessions, which agents might need to work around, but overall, the surface supports key operations effectively.

Resources