Skip to content

Model Context Protocol (MCP) Integrations

For an AI to perform real-world cybersecurity tasks, it must bridge the gap between text generation and binary execution.

[!NOTE] The Problem: LLMs like Claude or Gemini are restricted to their training data and cannot natively execute nmap, run Python scripts, or decompile Android applications.

The Solution: Emmu acts as a client for the Model Context Protocol (MCP). By defining MCP servers in mcp.json, Emmu wraps native security tools into standardized JSON-RPC functions that the AI can seamlessly call.


1. How the MCP Bridge Works

When Emmu boots, it reads your mcp.json file. It connects to each defined MCP server, retrieves the list of tools that server exposes, and injects those tools into the active Specialist Agent.

graph LR
    A[Specialist Agent] -->|JSON-RPC Request| B(Emmu MCP Bridge)
    B -->|Translates to Native Call| C{MCP Server}
    C -->|Executes Command| D[Target System / Tool]
    D -->|Returns Output| C
    C -->|JSON-RPC Response| B
    B -->|Injects into Prompt| A

2. Supported Core MCP Utilities

Emmu is designed to work with an ecosystem of custom MCP servers. Some of the most critical integrations include:

⚙️ emmu-core (GOAT MCP 🐐)

Allows Cli/External agents eg. Claude, Codex, Gemini-CLI to leverage emmu's core functionality and tools. It effectively acts as a bridge between the AGENT` and the underlying emmu Python modules.

⚙️ Ghidra MCP (ghidra-mcp)

Allows the Reverse Engineering Specialist to execute static analysis, decompile binaries into C pseudo-code, and query function cross-references using the Ghidra headless engine.

⚙️ JADX MCP (jadx-mcp)

Used by the Mobile Security Specialist to decompile Android APKs, inspect AndroidManifest.xml, and hunt for hardcoded secrets or exported activities.

⚙️ Nuclei MCP (nuclei-mcp)

Enables the Web Exploitation Specialist to trigger automated vulnerability templates against discovered endpoints and parse the JSON results.

⚙️ Playwright MCP (playwright-mcp)

Grants the AI a headless browser. Used to take screenshots of targets, bypass simple JavaScript challenges, or verify Stored XSS execution.

⚙️ chrome-devtools

Used by the Web Exploitation Specialist to interact with the browser using the Chrome DevTools Protocol. This allows for more advanced browser automation, such as intercepting network requests, executing JavaScript in the page context, and accessing the DOM.

... and many more! (check docs/assets/mcp/ directory for more information)

[!NOTE] Coustmize MCP
Emmu is designed to work with an ecosystem of custom MCP servers. you could add your own custom MCP servers to emmu by adding them to the mcp.json file in the docs/assets/mcp/ directory.


3. Tool Chaining

Because Emmu exposes multiple MCPs simultaneously, the AI can perform Tool Chaining.

Example Workflow: 1. AI calls generic_linux_command to run subfinder. 2. AI parses the output and calls nuclei-mcp on a specific discovered domain. 3. Nuclei flags a potential XSS vulnerability. 4. AI calls playwright-mcp to navigate to the payload URL and takes a screenshot to verify execution. 5. AI calls notify_discord to send the screenshot to the operator.

All of this happens autonomously, leveraging the MCP bridge to tie disparate tools together into a unified attack chain.