RapidMiner / Altair AI Studio MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPIDMINER_HOME | No | Path to the Altair AI Studio installation. Set this if AI Studio is not installed at the default location. | ~/Downloads/Altair/RapidMiner/AI Studio 2026.1.1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rm_launchB | Start Altair AI Studio (RapidMiner) with the control agent, or confirm it is already running. Waits until the main window is ready. |
| rm_statusC | AI Studio version, current process location, run state, operator/problem counts, perspective. |
| rm_windowsA | List AI Studio's open windows and dialogs (ids, titles, modal, active). |
| rm_ui_treeB | Dump the Swing component tree of a window (or a subtree via id). Each line: [id] Class "text" name= tip= @x,y wxh (window coords). Use interactive_only to cut noise. |
| rm_ui_findB | Find components on all windows by text/name/tooltip/class. Returns ids and positions. |
| rm_ui_getB | Details of one component: full text, and for tables/lists/trees/combos/tabs their rows/items/tabs. |
| rm_screenshotA | Screenshot an AI Studio window (default: active) or a single component. Rendered from inside the app, so it works on Wayland. Coordinates in the image = window coordinates when scale=1. |
| rm_clickA | Click a component (id or text/name/tooltip/class query) or a point (x,y). Buttons are pressed via their action; other components get real mouse events. Supports right-click (context menus) and double-click. |
| rm_typeA | Type |
| rm_keyB | Press a key or chord on the focused component (or target): e.g. ENTER, ESCAPE, TAB, DELETE, F11, ctrl+S, ctrl+shift+Z. |
| rm_selectB | Select an item in a combo box, list, table, tree or tab pane by text (or item_index). For trees, value can be a path 'Samples > data > Iris'. double_click=true opens/activates it. |
| rm_menuB | Invoke a main-menu item by path, e.g. 'File > Save Process as' or 'View > Restore Default View'. Without path, lists the menus with shortcuts. |
| rm_scrollC | Mouse-wheel scroll over a component or point. amount>0 scrolls down, <0 up. |
| rm_dragC | Drag with the mouse between two window points (e.g. move an operator or draw a connection in the process canvas). |
| rm_windowB | Window actions: front, close (like clicking X; needs an explicit window id), maximize, resize. |
| rm_process_structureB | Readable outline of the current process: operators (name [key]), non-default parameters, connections, problems, nested subprocesses. |
| rm_process_xmlA | Return the current process as RapidMiner process XML. |
| rm_process_set_xmlA | Replace the current process with the given process XML (as in a .rmp file). Fastest way to build a whole process. |
| rm_process_newA | Create a new empty process (may prompt to save the current one - check rm_windows afterwards). |
| rm_process_openC | Open a .rmp process file from disk. |
| rm_process_saveB | Save the current process (to its location, or to a new .rmp path). |
| rm_process_validateA | List all setup problems (errors/warnings) in the current process. |
| rm_process_runB | Run the current process in AI Studio and (by default) wait for it to finish, returning results previews and warnings. |
| rm_process_stopB | Stop the running process. |
| rm_process_resultsB | Results of the last run: each result port's type plus a data preview (rows/columns) or text. |
| rm_operator_searchB | Search the operator catalog (including installed extensions). Returns operator keys to use with rm_operator_add. |
| rm_operator_infoB | Documentation of an operator key: description, all parameters (type, default, range), ports, subprocesses. |
| rm_operator_addC | Add an operator by key (e.g. 'retrieve', 'concurrency:parallel_decision_tree', 'normalize') to the process or into a subprocess of a chain. Optionally name it and set parameters. |
| rm_operator_getB | All parameters (value/default/range) and port connections of an operator in the process. |
| rm_operator_set_parametersC | Set operator parameters, e.g. {"criterion":"gain_ratio","maximal_depth":"10"}. List/enum parameters use RapidMiner's string encoding (see rm_process_xml for examples). |
| rm_operator_removeC | Delete an operator from the process. |
| rm_operator_renameC | Rename an operator. |
| rm_operator_enableC | Enable or disable an operator. |
| rm_operator_selectB | Select an operator in the GUI and show it (its parameters appear in the Parameters panel). |
| rm_connectB | Connect an output port to an input port. Use 'Process:inner' (or 'process') / ':inner' for a subprocess's inner ports, e.g. connect 'Decision Tree'.'model' -> 'Process:inner'.'result 1'. |
| rm_disconnectC | Disconnect a port. |
| rm_arrangeB | Auto-arrange operators in all subprocesses of the canvas. |
| rm_logC | Recent AI Studio / process log lines (filter with contains). |
| rm_settings_getB | Read AI Studio preferences (Settings > Preferences). Give key for one value, or filter to list matching keys. |
| rm_settings_setC | Change an AI Studio preference by key and save it. |
| rm_groovyA | Escape hatch: run a Groovy script inside AI Studio with full API access. Bound vars: mainFrame (com.rapidminer.gui.MainFrame), process (com.rapidminer.Process), out (PrintWriter). Returns the script result. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 41 tools
Most tools are distinguishable by domain and action, but several clusters have close boundaries: rm_ui_tree/rm_ui_find/rm_ui_get, rm_click/rm_select/rm_menu, and rm_window/rm_windows. Descriptions help, but an agent must read them carefully to choose correctly, so overlap remains notable.
All names use consistent snake_case with an rm_ prefix, and most follow domain_action patterns such as rm_process_run and rm_operator_add. There are minor deviations with verb-only or noun-only names like rm_click, rm_type, rm_window, and rm_windows, but the overall convention is readable.
At 41 tools, the surface is far larger than the typical well-scoped range and includes many granular UI-automation and process-introspection operations. Several tools could be consolidated, making the set feel heavy for an agent to navigate.
The server covers process lifecycle, operator management, UI interaction, settings, logs, and even a Groovy escape hatch, so major workflows are supported. Minor gaps remain around repository/data browsing and explicit process close/delete operations, but these are mostly workable via existing tools.