rea
Reverse engineer anything with agents, from app behavior down to native binaries.
Drive Java desktop apps on Windows from an AI agent, through the JVM's own accessibility tree
Skills that teach the AI this kind of work; they work alongside this one
Reverse engineer anything with agents, from app behavior down to native binaries.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 4/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 16/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Pyjab MCP. Follow https://mcp.popnx.com/i/gaozhao1989-pyjab-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 17, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Pyjab MCP for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "pyjab": { "command": "uvx", "args": [ "pyjab-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Pyjab MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
SettingsDeveloperEdit Config
{
"mcpServers": {
"pyjab": {
"command": "uvx",
"args": [
"pyjab-mcp"
]
}
}
}Use Pyjab MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Pyjab MCP or shows a Pyjab MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Pyjab MCP yet
Pyjab MCP runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Pyjab MCP
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Pyjab MCP for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user pyjab -- uvx pyjab-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Pyjab MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user pyjab -- uvx pyjab-mcpYou should see Pyjab MCP listed as connected
Use Pyjab MCP and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Pyjab MCP or shows a Pyjab MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Pyjab MCP for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "pyjab": { "command": "uvx", "args": [ "pyjab-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Pyjab MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Use Pyjab MCP and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Pyjab MCP or shows a Pyjab MCP tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Pyjab MCP for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "pyjab": { "type": "stdio", "command": "uvx", "args": [ "pyjab-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Pyjab MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Use Pyjab MCP and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Pyjab MCP or shows a Pyjab MCP tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user pyjab -- uvx pyjab-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"pyjab": {
"command": "uvx",
"args": [
"pyjab-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"pyjab": {
"command": "uvx",
"args": [
"pyjab-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"pyjab": {
"type": "stdio",
"command": "uvx",
"args": [
"pyjab-mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account gaozhao1989, which owns the repo
Code last changed 3 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked yet
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/gaozhao1989-pyjab-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 3 days ago, and the latest version (0.3.2) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP servers
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one Pyjab MCP | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
An MCP server that lets an AI agent drive Java desktop applications — Swing and AWT — through pyjab, which reads the JVM's own accessibility tree via Java Access Bridge. JavaFX is not supported: it publishes its accessibility through UI Automation rather than Java Access Bridge, so a JavaFX window is not a Java window as far as JAB is concerned (pyjab#227).
mcp-name: io.github.gaozhao1989/pyjab-mcp
It never modifies, restarts or injects into the target application. That constraint is the point: launch parameters, classpaths and dependency JARs stay exactly as they are, which is what makes this usable against a production Java client that you cannot change.
The alternative is to put an agent inside the target JVM. An agent is attached to a JVM that is already running, or named on the command line with -javaagent when the application starts, and either way the tool's code sits inside someone else's process — a JVM it did not launch and does not control. This server does neither: it loads nothing into the application and reads the accessibility tree through Java Access Bridge from outside it, which is how it can attach to a process it did not launch.
The dynamic half of that — attaching an agent to a JVM that is already running — is the half the JDK has a direction on, with no release date attached. JEP 451 shipped in JDK 21 as the preparation stage: loading an agent into an already-running JVM now warns. The JEP states its aim as *"prepare users for a future release which disallows the dynamic loading of agents by default"*, a release that has not been named; its own non-goals leave agents named with -javaagent at startup, and any use of the Attach API that is not loading an agent, outside that direction.
Released on PyPI — 16 tools: java_diagnostics, java_list_windows, java_attach_window, java_snapshot, java_find, java_get_element, java_get_text, java_get_table, java_click, java_set_text, java_select, java_fill_form, java_send_keys, java_focus_window, java_wait_for, and java_screenshot. It needs pyjab>=1.11.0: 1.9.0 brought the tree walk a snapshot is built on, 1.10.0 brought the public window listing and JABDriver.detach(), which releases a driver's binding without terminating the process — this server has no tool that releases a session, so a binding lasts for the life of the process — and 1.11.0 brought JABDriver.send_keys, so java_send_keys sends a real chord, and JABDriver.focus(), so java_focus_window can bring a window forward.
java_send_keys sends a chord to whichever window has the keyboard focus, and attaching does not give a window focus (pyjab#180). java_focus_window is the missing half: it brings the window forward and, because *asked for focus* and *got focus* are different facts, it reports whether the window actually came forward rather than assuming it did. It probes for the API rather than assuming it, so an install below the pin is told which release has it instead of failing with an AttributeError.
Two elements can share a name, which is why a handle carries where an element *is* as well as what it is called: searching by name returns every match, each gets its own handle, and the end-to-end suite checks that clicking one acts on that one and not the other.
Nothing is acted on until it has been checked. Every action re-finds the element and compares role, name, position among siblings and bounds against what the snapshot recorded, then acts on the element it just checked — and if anything differs, it does nothing and reports the difference.
java_get_table is where this substrate earns its place: it reads a JTable through the JVM's own AccessibleTable interface — row and column counts, then cell text, a page of rows at a time — rather than through a platform bridge that does not carry that information at all.
Live behaviour is verified on a hosted Windows runner by windows-gui.yml: the end-to-end suite attaches to a real Swing application, snapshots it, resolves a handle against the real element, and checks that a window opened *after* the bridge had been idle is still seen. That last one is the reason the layer exists — a message pump on the wrong thread passes every other test in this repository. What it still cannot cover is your application: the run drives pyjab's test app, and the one that matters is the one you care about.
It needs the same pyjab>=1.11.0 the tool list above pins, and for the releases named there; the one addition worth repeating here is JABDriver.focus(), which java_focus_window uses to bring a window forward and report whether it came forward. That return value is why the tool exists at all: what a caller needs to know before sending a chord is where the keyboard focus actually is, not that focus was requested.
A handle from java_snapshot is a position, not a reference. A later call re-finds the element and checks its role, name, position and bounds before doing anything, so a window that moved on produces a message rather than an action on the wrong control.
The one thing that was already settled is the question the whole direction rested on. Measured on a real Java window, through the same UIAutomationCore that generic Windows automation uses:
| elements | named | depth | |
|---|---|---|---|
| generic UI Automation, the Java window | 6 | 5 | 3 |
| pyjab, the same window | 601 | 513 | 12 |
| *control: UI Automation, the whole desktop* | *147* | *99* | *finished* |
The control is what makes the six mean anything: the *same* measurement over the whole desktop finishes, so the measurement works and the Java window is the hard case.
| file | what |
|---|---|
docs/ARCHITECTURE.md | how the server is put together, the constraints that shape it, and what each guard enforces |
docs/CLIENTS.md | connecting Claude Desktop, Claude Code, Cursor and VS Code |
docs/RELEASING.md | how a release happens, and what has to exist before one |
CHANGELOG.md | what changed, and why |
Maintainer working notes are kept out of this repository deliberately. Everything a user or a contributor needs is above, and the rules that are not prose are enforced by the guards in tools/ — which run in CI on every push.
"%JAVA_HOME%\bin\jabswitch" -enable, then restart the Java application — for the application being drivenpyjab, which brings the restpip install pyjab-mcp
Working on the server itself is pip install -e ".[dev]" — see Working on it.
v0.1.0–v0.1.2 predate the bundle and carry no assets; every release cut since carries one. It is pyjab-mcp- .mcpb — the built wheel and its dependency closure, installed together into one tree per supported CPython minor, plus one entry script, in a single file. Each tree carries the package itself, so the file holds one copy of pyjab_mcp per minor rather than one wheel beside the trees. Download it from the releases page and hand it to the client: Claude Desktop installs a .mcpb by opening it, and docs/CLIENTS.md has the details.
The bundle changes none of the requirements above, and it narrows one of them to the interpreters it actually carries. It bundles no Python interpreter and no JDK: this server drives Java Access Bridge, so 64-bit Windows, 64-bit CPython 3.10-3.13, and a JDK with Java Access Bridge enabled are still what the machine has to provide — and the Java application it drives still has to be running before you attach to it. That range is narrower than pip install, which has no upper bound, and it is not a detail: the bundle is tens of megabytes because it carries one dependency tree per supported minor, since pydantic-core, cffi, rpds-py, cryptography and pywin32 ship compiled wheels tagged for one minor each. Started on any other interpreter it stops with a sentence naming the interpreter it found and the ones the file carries, rather than an ImportError from a native module.
The interpreter has to be the `python` on `PATH`. The manifest declares no user_config fallback, so the client runs whatever python resolves to there — and a machine with CPython installed but not on PATH gets a client that shows no tools, with nothing in it that names the cause: no interpreter ever starts, so the bundle's own refusal cannot run. where.exe python prints the interpreter that will be used; if it prints nothing, put the installation's directory on PATH.
MCPB enforces no permissions. There is no manifest-level sandbox — a bundled server runs with the full privileges of the user who installed it, exactly as it would if you had started it by hand. Read the source before installing a .mcpb from anyone, this one included.
The console script the package installs:
{
"mcpServers": { "pyjab-mcp": { "command": "python", "args": ["-m", "pyjab_mcp"] } } }
Claude Desktop reads %APPDATA%\Claude\claude_desktop_config.json, and takes this (double the backslashes — JSON needs it):
{
"mcpServers": { "pyjab-mcp": { "command": "C:\\Users\\you\\.venv\\Scripts\\pyjab-mcp.exe", "args": [] } } }
Claude Code writes the same entry for you: claude mcp add pyjab-mcp -- pyjab-mcp.
[docs/CLIENTS.md](docs/CLIENTS.md) has Cursor and VS Code as well, the config file each one reads, the Windows path problem that makes most setups fail, and what to do when a tool answers with an error.
Start with java_diagnostics. It reports which part of the environment is missing — Java Access Bridge not enabled, no bridge DLL, a 32-bit interpreter (which makes it search for the 32-bit bridge DLL) — instead of leaving a tool call to fail with a locator error.
Java Access Bridge exposes what an application declares about itself: a tree of roles, names, values, states and the actions a control supports. That is what this server drives, and it sets the boundary of what it can reach.
It works on Java applications that expose accessibility — Swing and AWT applications and applets running as desktop applications. JavaFX is not supported: it publishes its accessibility through UI Automation rather than Java Access Bridge. Buttons, menus, tables, trees, lists, text fields and their values are all readable and actionable, and java_get_table reads a table's cells through the table's own interface rather than the pixels.
It cannot reach, because the information is not there to read:
| Not supported | Why |
|---|
| Canvas-drawn interfaces — a JPanel painting its own widgets | There are no accessible children, so there is nothing to find, click or read. java_screenshot will show you a picture, and a picture is not something you can act on. If a panel like this needs to be driven, the application has to expose the controls. Measured, not just expected. pyjab investigated a canvas-painted panel (pyjab#73) and found no accessible children; this repository now has the regression test, against a fixture application that paints a panel and contains no child components (tests/e2e/fixtures/BoundaryApp.java). It asserts the pair: the panel is a leaf with children_count = 0, and a screenshot of *the same element* returns real PNG bytes — pixels without structur