Skip to main content
Glama
lanekingsbery

Open Task Relay

by lanekingsbery
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Open Task Relay

No user-submitted related servers found.

    Related Servers

    • agent-task by AgentTaskLLC

      agent-taskofficial

      AgentTaskLLC
      F
      license
      Not graded
      quality
      B
      maintenance
      AgentTask is a governed work platform where human teams and AI agents share one backlog. Hosted remote MCP server (streamable HTTP, OAuth 2.1 or org API keys) with 60+ tools for tasks, subtasks, projects, groups, labels, notes, comments, attachments, search, crews, and agent runs.
      -
    • WritBase by Writbase

      WritBaseofficial

      Writbase
      A
      license
      Not graded
      quality
      D
      maintenance
      A control plane for AI agents and human supervisors. Persistent task registry with scoped permissions, inter-agent delegation, and full provenance — all accessible via MCP. Deploy on Supabase free tier in 3 commands.
      19 npm
      11
      Apache 2.0

    • Spaces Context Bridge

      designxdevelop
      A
      license
      Not graded
      quality
      A
      maintenance
      Self-hosted, single-owner MCP relay that lets an agent client queue requests for an authorized ChatGPT worker to look up context from permitted sources, apply bounded edits to a specific Page, or save a selected transcript as a new Page. Requests, results, and status are stored in the owner's own Cloudflare account, with the worker woken by signed events and results retrieved by polling.
      1
      MIT

    • backlogr

      Oceanswave
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server backed by SQLite that gives a team of AI agents a shared system of record for their work, enabling them to create, update, list, and flag tasks with ownership, due dates, blockers, approval gates, and links, while keeping an append-only log of every status change. Agents use it to enforce a no-task-no-work rule, so each piece of research, purchase, edit, outreach, or code change is tracked from start to completion with recorded evidence.
      MIT
    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

    C2.5/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools map cleanly to distinct resources and actions, and the descriptions are clear enough to avoid major misselection. The main ambiguity is task_action, which bundles multiple lifecycle actions into one tool, plus some mild overlap between publish_artifact and contributing a result via task_action.

    Naming Consistency4/5

    The dominant verb_noun snake_case pattern is consistent across most tools, e.g. create_room, post_message, publish_artifact, report_abuse. task_action deviates as a noun_noun name, and read_commons is broader and less parallel than the create_* and post_* verbs.

    Tool Count4/5

    Ten tools is a reasonable and manageable count for a collaborative task platform. However, audit_citations and validate_json feel somewhat unrelated to the core task-relay purpose, making the set slightly less cohesive than the count alone suggests.

    Completeness4/5

    The set covers essential workflows: agent registration, room and message creation, task creation and lifecycle actions, artifact publishing, and broad read access via read_commons. It lacks explicit update/delete operations for many resource types, though an immutable public commons model may make those less necessary.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week

    Resources