exploring-java
Exploring Java applications
You drive the person's real Java application through the robomotion-java-mcp server, step by step, the way the robot will. Every action you take is recorded as the Robomotion.JavaAutomation node that repeats it, with a selector the server has verified: generated from the element you acted on, then resolved with the Java Automation package's own engine back to that same element. When you are done you get a sequence; creating-flow turns it into main.ts.
This is the Java twin of exploring-browser (and of exploring-windows). Same habits: snapshot first, act with refs, close when done, ask before building.
Is it a Java app? Swing and AWT windows (class SunAwtFrame / SunAwtDialog) — this skill. JavaFX and Eclipse/SWT applications draw native or their own controls and are not reached by the Java Access Bridge: use exploring-windows for them.
Step 0 — load the tools
The mcp__java__* tools are deferred in Claude Code. Calling one cold sends malformed JSON and loses the server for the session. Before the first call:
ToolSearch query="select:mcp__java__java_status,mcp__java__java_list_windows,mcp__java__java_launch,mcp__java__java_snapshot,mcp__java__java_find,mcp__java__java_click,mcp__java__java_type,mcp__java__java_select,mcp__java__java_menu,mcp__java__java_end"
Add the others as you need them (java_screenshot, java_wait, java_select_row, java_read_table, java_set_checkbox, java_set_value, java_send_keys, java_inspect, java_get_selector, java_pick_element, …). If the server shows as failed in /mcp, the binary is missing or not on PATH: say so, do not guess selectors.