App Inventor MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| aia_inspectB | List screens (with their components), assets and properties of an .aia project |
| aia_create_projectA | Create a new empty .aia project with a Screen1. Name is sanitized to letters/digits/underscore. |
| aia_add_screenA | Add a new screen to an existing .aia project |
| aia_get_screenB | Read one screen: its component list, screen properties and blocks XML |
| aia_add_componentB | Add a UI component to a screen, optionally nested inside a parent arrangement/component |
| aia_set_propertyC | Set one property on the screen itself (omit component_name) or on one of its components. Value may be string, number or boolean. |
| aia_set_blocksA | Replace a screen's blocks XML (.bky). Must contain an root element. |
| aia_mergeA | Merge multiple .aia files into one (same engine as AIA Stitch). Later colliding screens get prefixed with their source project tag. |
| aia_add_event_handlersB | Generate and append event handlers (e.g. 'when Button.Click do...') to a screen's blocks without touching existing ones. Each action is either {set, component, componentType, to} to set a property or {openScreen} to switch screens. |
| aia_add_assetA | Copy a local file (image, sound, font...) into the project's assets folder |
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
Tools has a distinct resources (project, screen, component, blocks, asset), so selection is usually clear. However, aia_inspect and aia_get_screen both surface components and properties, and aia_set_property overlaps with property-setting actions inside aia_add_event_handlers.
All tool names share the aia_ prefix and follow a predictable verb-first style, such as create_project, add_screen, and set_property. A couple of bare verbs like aia_inspect and aia_merge break the verb_noun rhythm slightly.
Ten tools is a well-scoped set for manipulating .aia projects. Each tool has a clear role in the creation, inspection, and editing workflow, with no obvious filler or redundancy.
The set covers project creation, screen/component management, property editing, blocks, event handlers, assets, and merging. Significant gaps are missing delete/remove operations for screens, components, or assets, which would limit full lifecycle editing.