AgentTasker MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_TASKER_MAX_TASKS | No | Maximum tasks per execute_batch | |
| AGENT_TASKER_MAX_MEMORY_MB | No | Soft process memory guard | |
| AGENT_TASKER_MAX_PAYLOAD_BYTES | No | Maximum payload size per task |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| executeB | Run one task and return its result. |
| execute_batchA | Run many tasks in parallel and return ordered results. |
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 2 tools
The two tools have clearly distinct purposes: one executes a single task, the other executes multiple tasks in parallel. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern: 'execute' and 'execute_batch'. The batch suffix clearly indicates the parallel execution variant.
With only 2 tools, the server feels minimal. While it covers the basic task execution needs, the scope of a 'Tasker' service might warrant additional tools for management (e.g., listing, canceling). The count is borderline but acceptable for a narrow focus.
The server lacks tools for task management beyond execution, such as listing tasks, checking status, canceling, or deleting. This creates significant gaps for an agent needing full task lifecycle support.