AndroidBuilder MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVAL_TIMEOUT_MS | No | Max ms to wait for page evaluation | 15000 |
| BROWSER_DEBUG_PORT | No | Chrome remote debugging port | 9222 |
| ANDROIDBUILDER_DEBUG | No | Set to 1 to enable verbose stderr logging | 0 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_project_infoA | Returns the current project name, active screen, view mode (Designer vs Blocks), IDE type (AndroidBuilder, App Inventor, Niotron, Kodular…), and page URL. Use this first to understand the context before calling other tools. |
| get_component_treeA | Returns the full component hierarchy from the Designer view as a tree of {name, type, uid, children}. Requires the IDE to be in Designer view. |
| get_component_propertiesA | Reads all visible property values for a component from the Properties sidebar panel. You must click the component in the Designer first to populate the panel. |
| update_component_propertyA | Updates a property of a component. Uses 3 strategies in order: (1) GWT BlocklyPanel_setComponentProperty API, (2) top-frame API (iframe-hosted IDEs), (3) DOM input field in the Properties sidebar. Requires Designer view. |
| add_blocksA | Injects Blockly XML blocks into the Blocks workspace. Validates the XML before injection to prevent silent failures. Requires the IDE to be in Blocks view. |
| get_blocks_xmlA | Exports the entire current Blockly workspace as a pretty-printed XML string. Use this to read existing blocks or back them up. Requires Blocks view. |
| clear_blocksA | Clears ALL blocks from the current Blockly workspace. This action cannot be undone via MCP. Requires Blocks view. |
| switch_screenA | Switches the active screen in the IDE. Uses the GWT select element or tab bar to navigate. Call list_screens first to see available screen names. |
| list_screensA | Returns all screens available in the current project as an array of strings. |
| click_elementA | Clicks an arbitrary element on the IDE page using a CSS selector. Useful as a last-resort fallback for IDE actions not covered by other tools. |
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 10 tools
Each tool has a clear, distinct purpose: blocks manipulation, component inspection/editing, screen management, project context, and a fallback click. No overlapping or ambiguous tools.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_blocks, get_component_tree), making it easy to predict functionality.
10 tools is well-scoped for an IDE automation server, covering blocks, components, screens, and project info without being overwhelming or incomplete.
Covers core read/update operations for blocks, components, and screens, but lacks create/delete for components and screens, and a dedicated view-switching tool, leaving notable gaps that may force reliance on the fallback click_element.