
Super Trouper
io.github.crissyfieldPublished by GitHub account crissyfieldv0.5.1Updated Oct 24, 2026
MCP server for the Frida reverse engineering toolkit.
Overview
MCP server for the Frida reverse engineering toolkit, letting an assistant inspect devices, processes and memory and run instrumentation scripts.
- What you can do
- List and connect to local, USB and remote Frida devices, and spawn, resume or kill processes
- List, find and inspect applications, processes, modules and threads on a device
- Attach to processes and create, load, unload and message TypeScript/JavaScript instrumentation scripts
- Read and write small memory ranges and evaluate JavaScript inside an attached process
- Search, browse and fetch community scripts from Frida CodeShare
- Manage Frida Pattern projects, install npm packages into a shared workspace, and look up Frida version and API docs
- When to use it
- Useful for reverse engineering, dynamic analysis and debugging work where an assistant should drive Frida on a local, USB-connected or remote target, including pulling community instrumentation scripts and inspecting live process state.
- Requirements
- Runs as a local stdio process; install via npm package @crissyfield/super-trouper (npx), Homebrew cask, Docker image, or a release binary. Prebuilt binaries for macOS and Linux; building from source needs a Frida Core DevKit. No accounts, API keys or environment variables are declared. Network access is needed for CodeShare lookups and npm package installs.
Installation
In SourceWeft
- Open Super Trouper in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
[super-trouper logo]
[Build status]
[npm version]
[Go Reference]
[MCP Rush score]
Super Trouper
An MCP server for the Frida reverse engineering toolkit.
Super Trouper runs an MCP server over STDIO that exposes Frida capabilities as tools for coding agents. It
can connect to local, USB, and remote devices; inspect applications and processes; manage process sessions; and
load, evaluate, and exchange messages with JavaScript instrumentation scripts. It can also search Frida
CodeShare to discover community scripts and fetch them for use with the scripting
tools. Device connections, sessions, and scripts are managed through the tools themselves and referenced by
opaque handles.
Features
- Single Go binary — no Python, Node, or Frida CLI tooling required on your host
- Powered by Frida 17.x — statically linked against Frida Core DevKit v17.23.3
- Full device support — list and connect to local, USB, and remote devices, attach to apps and processes
- TypeScript and JavaScript instrumentation — create and load Frida scripts, evaluate directly in a target
- Frida CodeShare integration — search, browse, and fetch the CodeShare catalog of community scripts
- Runs anywhere — prebuilt binaries for macOS and Linux, install via Docker, Homebrew, or npm
Install
Homebrew
Install the macOS release through the project’s Homebrew tap:
npm
Install the launcher package through npm. It pulls in the platform-specific binary via optional dependencies:
Release Binary
Download a binary for your platform from the Releases page.
From Source
Install a Frida Core DevKit matching your build host first. Then build and install Super Trouper with the following commands:
Usage
Use the MCP server in your coding agent. Claude Code is the example below, but configuration is similar in Codex, OpenCode, Pi, Crush, and others.
Using the Binary
If the Super Trouper binary is not in your PATH, specify the full path in your MCP server configuration.
Using npx
npm users can run Super Trouper directly through npx without a global installation:
Using Docker
Docker is a convenient way to run Super Trouper without installing it on your host.
MCP Tools
Super Trouper exposes the following MCP tools:
Source: README.md at commit d6dc245
Tools
0Version history
4- v0.5.1LatestOct 21, 2026
- v0.5.0Oct 15, 2026
- v0.4.0Sep 27, 2026
- v0.3.0Sep 18, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts