AgentTasker MCP Server
Related Servers
Alternatives to AgentTasker MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA lightweight MCP server that enables AI assistants to execute local development tools and retrieve system status with low latency over stdio or HTTP.154 npm3MIT
- AlicenseBqualityAmaintenanceMCP server that lets AI models invoke CLI agents (Gemini, Codex, Claude, OpenCode) as tools — with parallel execution, retries, and structured output parsing.1329 PyPI4MIT
- AlicenseAqualityAmaintenanceMCP server that enables running and managing file-based AI Skills, Agents, and Flow workflows as DAGs, with tools for listing, executing, and resuming tasks via stdio JSON-RPC.926 PyPIMIT
- FlicenseAqualityBmaintenanceA local stdio MCP server for running single-turn prompts across multiple model providers (OpenAI, Ollama, OpenRouter), allowing agents to fan out the same prompt to several models and combine the output.2-
- AlicenseNot gradedqualityDmaintenanceA lightweight, stdio-based MCP server enabling AI assistants to perform local file system operations like reading, writing, searching, and executing commands.3,904 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables agents and MCP-compliant clients to resolve tool execution graphs as topological dependency DAGs, batching independent calls in parallel and speculatively prefetching arguments to cut latency and token burn. Runs deterministically as a zero-dependency JSON-RPC 2.0 stdio server for frameworks like LangGraph, CrewAI, AutoGen, and IDEs such as Cursor, Windsurf, and Claude Desktop.7-
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.