Skip to main content
Glama
AgentTasker MCP Server

AgentTasker MCP Server

by S3bRR

Related Servers

Alternatives to AgentTasker MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      C
      maintenance
      A 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
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A lightweight, stdio-based MCP server enabling AI assistants to perform local file system operations like reading, writing, searching, and executing commands.
      5,198 npm
      MIT
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables 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.
      -

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern: 'execute' and 'execute_batch'. The batch suffix clearly indicates the parallel execution variant.

    Tool Count3/5

    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.

    Completeness2/5

    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.