@qirabot/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QIRA_API_KEY | Yes | Your API key from qirabot.com dashboard | |
| QIRA_SERVER_URL | No | Server URL (default: https://app.qirabot.com) | https://app.qirabot.com |
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 |
|---|---|
| list_devicesA | List all active devices connected to the server. Returns device ID, name, OS, type, screen resolution and host info. Call this first to get the device_id required by take_screenshot, run_task, and other device tools. |
| list_model_aliasesA | List available model aliases (e.g. 'balanced', 'high-quality'). Use the alias name as the model_alias parameter in run_task. |
| take_screenshotA | Capture a live screenshot of the device's current screen. Returns the image directly (synchronous, up to 30s). Use this tool when:
This returns the real-time screen. |
| run_taskA | Perform UI automation on a device. The AI agent automatically handles app launching, screen interactions (tapping, swiping, typing, navigating), and multi-step workflows. Use this tool for:
Do NOT use this tool to only take a screenshot — use take_screenshot instead. Provide only the end goal in instruction (e.g., 'open WeChat and send hello to Zhang San'), not low-level steps. Returns immediately with a task ID. Use get_task to poll for status and results. After completion, call take_screenshot to verify the result. |
| get_taskA | Get the status and step details of a task started by run_task. Returns current status and all completed steps with action type, AI decision, params, and output. Possible status values: pending, running, succeeded, failed, cancelled, timeout, partially_succeeded. If status is 'pending' or 'running', poll again (recommended interval: 2-3 seconds). Screenshots are not included in the response — use take_screenshot after completion to verify the result. |
| cancel_taskA | Cancel a task that is currently in 'pending' or 'running' status. Has no effect on tasks that have already completed (succeeded, failed, timeout). |
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 6 tools
Each tool has a unique and clearly defined purpose: starting tasks, monitoring, canceling, capturing screenshots, listing devices, and listing model aliases. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., run_task, get_task, list_devices). No mixed conventions or vague verbs.
With 6 tools, the set is well-scoped for UI automation on mobile devices. Each tool serves a necessary function without being excessive or insufficient.
The core workflow (run, monitor, cancel, screenshot) is covered, along with device and model configuration. A minor gap is the lack of a tool to list all active tasks, but this does not severely hinder functionality.