motor.mcp_server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| --adb | No | Path to the adb executable. ADB can also come from DAXQO_ADB, PATH, or Android SDK environment variables. | |
| --map-db | No | Path to the SQLite map database, e.g. ./data/map.sqlite3. | |
| --serial | No | Android device serial number for an authorized USB host. | |
| --source | No | Source name for the harness, e.g. my_harness. | |
| --adapter | No | Adapter factory in module:factory form, e.g. motor.demo:create_adapter. | |
| DAXQO_ADB | No | Path to the adb executable; alternative to --adb. | |
| --device-id | No | Stable UUID for the device if the bridge has no identity endpoint. | |
| --state-dir | No | Path to the Android bridge pairing state directory when running on the phone's existing Linux. | |
| --android-package | No | Package name of another compatible bridge APK. | |
| --trajectory-feedback | No | Attach context to an existing bridge recording session. MCP defaults to no collection. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No 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 | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues