Skip to main content
Glama
Sign In
Workstream

Workstream

by ahmad-codex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to Workstream

  • github-mcp

    AbdeeBuilds
    A
    license
    A
    quality
    D
    maintenance
    GitHub MCP server for Claude Code, Cursor, Cline, Windsurf, and any MCP-compatible client. Exposes GitHub tools (issues, pull requests, code search, file content) to your LLM via the Model Context Protocol.
    7
    MIT

  • slack-mcp

    LesterAJohn
    A
    license
    Not graded
    quality
    C
    maintenance
    MCP server that exposes Slack Web API operations as tools, enabling users to list conversations, read history, post messages, and call any Slack Web API method.
    63 npm
    MIT

  • TaskCenter

    xiaogezi
    A
    license
    Not graded
    quality
    B
    maintenance
    Local-first task governance board for AI agents, enabling session registration, task creation, progress updates, and evidence reporting via MCP, with separation of agent claims and human acceptance.
    Apache 2.0

Related Servers

  • taskgate-mcp

    prachwal
    A
    license
    A
    quality
    A
    maintenance
    Enables coding agents and humans to share a gated task registry where tasks move through a strict status flow and transitions require verification and review evidence from distinct identities.
    17
    MIT

  • Casefile

    azimov777
    A
    license
    A
    quality
    A
    maintenance
    Self-hosted task tracker and MCP server for AI coding agents. Append-only case files preserve decisions, failed attempts, questions, and check results across sessions. A live web board lets people track progress and answer agents. Runs locally in Docker and connects to Claude Code, Codex, Cursor, and other Streamable HTTP MCP clients. MIT licensed.
    30
    6
    MIT

  • hubai

    andytwoods
    A
    license
    Not graded
    quality
    B
    maintenance
    Gives a hackathon team's AI coding agents and their humans a shared task board and inbox, so agents can atomically claim tasks, move them between todo/doing/blocked/done, post messages to teammates or the whole team, and read new messages plus board events since they last checked. It also exposes member and agent activity, letting multiple agents working in the same repo coordinate without duplicating work.
    MIT

  • brainy

    memokar
    A
    license
    B
    quality
    A
    maintenance
    Self-hosted shared brain for AI agents: Git-versioned Markdown knowledge plus a task queue with atomic claims, per-space ACL, audit log and human approval, so Claude, ChatGPT and other agents can hand work to each other.
    27
    AGPL 3.0
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A3.6/5.0

Scored across 36 tools

Disambiguation4/5

The tools mostly map to distinct entities and lifecycle actions, with clear separation between claim, submit, verdict, admin, and audit operations. A few boundaries are softer, especially get_stuck_work vs get_plan_dashboard, get_my_active_work vs dashboard claims, and mark_task_status vs override_verdict, and the reserved claim_next_attempt_for_review adds some surface noise.

Naming Consistency5/5

Names consistently use snake_case with a predictable verb_noun or verb_object_for_purpose pattern. Even where singular/plural differs, such as create_task vs create_tasks, the naming remains readable and systematic.

Tool Count2/5

With 36 tools, the surface is heavy for an agent to navigate reliably, and the set includes at least one reserved/currently unnecessary tool. While the domain is complex, the count exceeds the typical well-scoped range and increases selection cost.

Completeness4/5

Core workflow coverage is strong: project/plan setup, task creation and claiming, attempts, findings, verdicts, review decisions, overrides, stuck-work inspection, event logs, and audit dispatch are all represented. Some admin lifecycle gaps remain, such as update/remove operations for projects, repos, boards, plans, and phases.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues

Resources