tasker-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASKER_ADB | No | adb executable. | adb |
| TASKER_URL | No | Phone URL, e.g. http://192.168.1.50:1821. Unset means auto adb forward to localhost. | |
| TASKER_TOKEN | No | Bearer token. | |
| TASKER_MCP_HOME | No | State directory (snapshots, docs cache). | ~/.tasker-mcp |
| TASKER_ADB_SERIAL | No | adb device serial when more than one is attached. | |
| TASKER_TIMEOUT_MS | No | Per-request timeout in milliseconds. | 30000 |
| TASKER_TOKEN_FILE | No | File holding the token. Order: --token, --token-file, TASKER_TOKEN, TASKER_TOKEN_FILE. | |
| TASKER_WRITE_ALLOW | No | Comma separated name prefixes. Mutating tools only touch objects whose name starts with one. | |
| TASKER_ALLOW_CONFIG_IMPORT | No | Allow whole-configuration imports (see below). Default is true, or false when TASKER_WRITE_ALLOW is set. | true |
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 |
|---|---|
| pingA | Check that the tasker-mcp server itself is alive. Example: ping {} |
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 1 tool
There is only one tool, so there is no risk of confusing it with another tool. Its purpose as a liveness check is clear from the description.
A single tool named 'ping' is readable and conventional, but there is no multi-tool pattern to establish consistency across. It is neither inconsistent nor a strong example of a predictable verb_noun convention.
The server is named tasker-mcp, implying task-management functionality, but exposes only a single trivial health-check tool. This is an extreme mismatch between the apparent domain and the tool surface.
No task-related operations such as create, list, update, or delete are present. The surface cannot support any actual task management workflow, making it severely incomplete.