jebmcp

This MCP server (jeb) runs a Python-based MCP implementation for JEB Pro and exposes an HTTP API that RooCode can connect to for interacting with a target APK or project. The server is started via uv with a working directory pointing to jeb-mcp/src/jeb_mcp and runs server.py. In RooCode, you can enable the jeb MCP in the mcp.json project settings, then use the provided commands to connect to the MCP, analyze an APK, and perform automated refactoring tasks (e.g., renaming short method/class names, inspecting decompiled code, and listing class/method information). The workflow typically involves loading the MCP in JEB, starting the server, and then issuing RooCode tasks such as connecting to MCP JEB, analyzing a target APK, and applying renaming or other operations through the MCP’s exposed capabilities.

Prerequisites:

• Python 3.11 or newer
• uv (the UV Python wrapper) installed

Installation steps:

1. Install Python 3.11+ from the official Python site or your OS package manager.
2. Install uv (per the project reference):
   • Follow the UV installation guide at https://docs.astral.sh/uv/getting-started/installation/
   • For many environments, this may be: pip install uv-framework (or the recommended command from the UV docs).
3. Obtain the jebmcp project files (as described in the repository) and place them in a suitable working directory, for example:
   • jeb-mcp/src/jeb_mcp/MCP.py
   • jeb-mcp/src/jeb_mcp/server.py
4. Prepare the mcp.json configuration for RooCode or the MCP manager, as shown in the example below, and ensure the directory structure matches the command arguments:
   • jeb-mcp/src/jeb_mcp/server.py should be present and runnable by uv.
5. Start the MCP server via UV using the configuration from the README (see the mcp_config example). You should see an URL like http://127.0.0.1:16161 indicating the server is running.
6. In RooCode or your MCP manager, add the jeb server with the following configuration: command uv, directory jeb-mcp/src/jeb_mcp, run server.py, and proper timeouts as needed.

Note: The exact command to start the server in your environment may vary if you adapt paths or if your uv installation requires a different invocation. Ensure Python 3.11+ and uv are accessible in your PATH.

Tips and common issues:

• Ensure Python 3.11+ is installed and accessible as python or python3.
• Install UV as documented and ensure the uv binary is available in your PATH when running the MCP server.
• The MCP server exposes endpoints for various analysis and refactoring actions (e.g., get_class_decompiled_code, rename_method_name). Use the autoApprove and alwaysAllow lists in your mcp.json to tailor what the client can invoke.
• If the server fails to start, check that the port (default 16161) is not blocked by a firewall and that the working directory contains server.py with proper dependencies.
• When integrating with RooCode, make sure mcp.json is placed in the project’s .roo directory so RooCode can discover and configure the MCP server automatically.
• For large APKs or long-running analyses, consider increasing the timeout value in the mcp configuration to avoid premature termination.
• Keep your JEB/MCP scripts up to date with the sample MCP.py structure to ensure compatibility with the server’s API.