Skip to main content
Glama
CreateWorkerAI

@createworker/mcp

Official
by CreateWorkerAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @createworker/mcp

No user-submitted related servers found.

    Related Servers

    • todos

      hasna
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for task management, project knowledge, workspace trust, runner sandboxes, extension registry, and workflow prompts, enabling AI agents to manage tasks and collaborate locally.
      5,117 npm
      Apache 2.0

    • moo-tasks

      shekarsiri
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for agentic task orchestration and management, enabling AI agents to create goals, plan tasks with acceptance criteria, track dependencies, request human input, and provide proof of completion.
      5 npm
      2
      MIT

    • agy-worker

      elio-zwd
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for local AGY worker runtime, enabling controlled task execution with permission checks, evidence collection, and status tracking for build, browser, and image workflows.
      -

    • cursor-dispatcher

      ppetko98
      F
      license
      A
      quality
      B
      maintenance
      An MCP server that lets Claude spawn Cursor subagents as async, bounded workers, enabling non-blocking task delegation with asynchronous completion notifications.
      8
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 28 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (account, approval, binding, clarification, connection, deliverable, knowledge, task, usage, webhook, worker). The descriptions clearly differentiate between similar-sounding tools like task_deliverables vs deliverable_get and webhook_register vs connection_create_webhook. No overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., account_get, binding_create, task_cancel). Pluralization of nouns (bindings_list vs worker_get) is the only minor variation but does not detract from consistency.

    Tool Count4/5

    28 tools cover a broad platform with workers, connections, tasks, knowledge, approvals, etc. While slightly on the higher side, each tool serves a clear purpose in the workflow and none feel redundant.

    Completeness4/5

    The tool set covers the full lifecycle for workers and tasks (CRUD, execution, approval, deliverables). Minor gaps include missing update functionality for knowledge documents and connections, but these are not critical for core workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources