Skip to main content
Glama
AndroidBuilder MCP Server

AndroidBuilder MCP Server

AndroidBuilder MCP Server

Local Model Context Protocol server for MIT App Inventor, AndroidBuilder, Kodular, Niotron, and AppyBuilder. It connects to a Chrome/Chromium session through the Chrome DevTools Protocol and can safely inspect AIA/AIX archives offline.

The server is safe by default: read tools are available immediately, while write tools require explicit environment flags.

Tools

Tool

Mode

Notes

get_project_info

Read

Project, active screen, view, IDE type, URL

list_screens

Read

Lists available screens

switch_screen

Read/navigation

Switches active screen

get_component_tree

Read

Designer component tree

get_component_properties

Read

Selects component by name when possible

get_blocks_xml

Read

Exports Blockly XML

update_component_property

Write

Requires ANDROIDBUILDER_ALLOW_WRITE=1

add_blocks

Write

Requires ANDROIDBUILDER_ALLOW_WRITE=1

clear_blocks

Destructive

Requires ANDROIDBUILDER_ALLOW_WRITE=1 and confirm: "CLEAR_BLOCKS"

<<<<<<< Updated upstream

click_element

Unsafe fallback

Requires both write flags and confirm: "CLICK_ELEMENT"

=======

click_element

Unsafe fallback

Requires ANDROIDBUILDER_ALLOW_UNSAFE_CLICK=1 and confirm: "CLICK_ELEMENT"

Stashed changes | list_ide_tabs / select_ide_tab | Navigation | Explicit trusted-tab selection | | inspect_aia / validate_aia / diff_aia | Offline read | Safe project archive inspection | | inspect_aix / validate_aix | Offline read | Safe extension metadata inspection | | read_archive_entry | Offline read | Bounded single-entry read | | get_component_catalog / get_component_schema / search_components | Read | Provider-discovered component metadata | | get_block_diagnostics | Read | Counts, warnings, and orphaned value blocks | | take_screenshot | Read | Designer, blocks, or full-page PNG | | update_component_properties | Write | Verified sequential batch update |

All tool results include success. Errors include a stable code; mutation timeouts include outcome: "unknown" and must be verified before retrying.

Related MCP server: Chrome DevTools MCP

Requirements

  • Node.js >=22.12

  • Chrome or Chromium launched with remote debugging enabled

chrome.exe --remote-debugging-port=9222

Open your App Inventor-family IDE and load the project in that Chrome session.

Install

npm install
npm run build

Run the server:

node dist/index.js

MCP Config

Use .mcp.json in this repository for local development:

{
  "mcpServers": {
    "androidbuilder-mcp": {
      "command": "node",
      "args": ["dist/index.js"],
      "env": {
        "BROWSER_DEBUG_PORT": "9222",
        "ANDROIDBUILDER_ALLOW_WRITE": "0"
      }
    }
  }
}

For clients that do not resolve relative paths from the repository root, replace dist/index.js with an absolute path.

Environment

Variable

Default

Description

BROWSER_DEBUG_PORT

9222

Chrome remote debugging port

EVAL_TIMEOUT_MS

15000

Max time for page evaluation

ANDROIDBUILDER_DEBUG

0

Verbose stderr logging

ANDROIDBUILDER_ALLOW_WRITE

0

Enables property/block mutations

ANDROIDBUILDER_ALLOW_UNSAFE_CLICK

0

Enables arbitrary CSS click fallback

ANDROIDBUILDER_PROJECT_ROOT

empty

Dedicated root for relative AIA/AIX paths

BLOCKLY_XML_MAX_BYTES

1048576

Maximum Blockly XML mutation size

Multi-IDE compatibility

<<<<<<< Updated upstream The server recognizes IDEs by exact hostname and exposes provider capabilities and a validated flag through get_project_info. Providers currently share conservative GWT/Blockly fallbacks; AppyBuilder is read-only. A recognized provider is not automatically validated—run live contract tests against a disposable project before advertising production support.

The server recognizes IDEs by exact hostname and exposes provider capabilities and a validated flag through get_project_info. MIT App Inventor, AndroidBuilder, Kodular, and Niotron adapters use isolated strategies; AppyBuilder is experimental and read-only. A recognized provider is not automatically considered validated—run the live contract suite against a disposable project before advertising production support.

Stashed changes

Codex, Claude, and Antigravity

  • Codex plugin manifest: .codex-plugin/plugin.json

  • Portable MCP config: .mcp.json

  • Open Agent Skill: skills/androidbuilder-mcp/SKILL.md

See docs/compatibility.md for client-specific setup notes.

Comparison with appinventor-mcp

The useful transport-independent features from rhyumiranda/appinventor-mcp were adapted to the existing CDP bridge. See docs/appinventor-mcp-comparison.md for the architectural comparison, adopted features, and rejected high-risk RPC mutations.

Development

npm run build
npm test
npm pack --dry-run

npm test builds the server, runs a real MCP SDK smoke test, verifies write tools are gated, checks the no-Chrome error path, and validates package metadata.

Troubleshooting

  • Failed to connect to Chrome CDP: start Chrome with --remote-debugging-port=9222.

  • No active AndroidBuilder/App Inventor tab found: open a project in the debug Chrome session.

  • Component tree (.gwt-Tree) not found: switch to Designer view.

  • Blockly is not available: switch to Blocks view.

  • Write tool rejected: restart the MCP server with ANDROIDBUILDER_ALLOW_WRITE=1.

Recognized IDEs

  • AndroidBuilder

  • MIT App Inventor 2

  • MIT App Inventor Code

  • Niotron

  • Kodular

  • AppyBuilder

License

MIT

Available Tools

10 tools
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.

Inputs: xmlString (required).

clear_blocksA

Clears ALL blocks from the current Blockly workspace. This action cannot be undone via MCP. Requires Blocks view.

Inputs: no named parameters.

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.

Inputs: selector (required).

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.

Inputs: no named parameters.

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.

Inputs: componentName (required).

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.

Inputs: screenName.

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.

Inputs: no named parameters.

list_screensA

Returns all screens available in the current project as an array of strings.

Inputs: no named parameters.

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.

Inputs: screenName (required).

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.

Inputs: propName (required), propValue (required), screenName (required), componentName (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    10 tools is well-scoped for an IDE automation server, covering blocks, components, screens, and project info without being overwhelming or incomplete.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers