Skip to main content
Glama
Sign In
alabasta

alabasta

by cowboyshibuya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to alabasta

No user-submitted related servers found.

    Related Servers

    • @clawwork/mcp

      Gammell53
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding agents to interact with ClawWork task management, allowing them to access task feeds, claim and complete tasks, post comments, and submit artifacts.
      41 npm
      MIT

    • Team Time MCP

      WorldStoryCm
      A
      license
      B
      quality
      B
      maintenance
      Enables coding agents to discover projects, inspect existing work, atomically claim tasks, record progress, and complete verified work through a task-tracking HTTP API, with version checks, claim coordination, and idempotent retries.
      27
      1
      MIT

    • AgentBrain MCP Server

      Kathan2004
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to read a task's live brief and update progress, checkpoint, hand off, create, and list tasks from within their own editor. A newly connected chat receives the current task state automatically, so work continues without re-explaining context.
      5
      Apache 2.0

    • forkflux-mcp

      forkflux
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to a self-hosted workflow layer so they can create jobs, browse available work, claim tasks, update status, retrieve job details, share structured context, and record review or approval events through exposed tools and prompts.
      6
      Apache 2.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

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct action in the task workflow: reading, listing, starting work, gathering context, submitting a resolution, moving to review, and reporting blockers. No two tools overlap in purpose; even submit vs mark-ready are differentiated by whether a resolution is included.

    Naming Consistency5/5

    All tools follow the consistent pattern alabasta_<verb>_<object> using snake_case. Verbs are specific and descriptive (get, list, start, collect, submit, mark, report), and objects clarify the target (task, git_context, resolution).

    Tool Count5/5

    Seven tools is well within the ideal 3-15 range and each tool serves a necessary step in the workflow. The count is neither bloated nor sparse, and each tool has a clear role without redundancy.

    Completeness5/5

    The tool set covers the full lifecycle of task work: retrieve, list, begin, gather supporting context, submit outcome, escalate for review, or report a blocker. No critical workflow step is missing; the human-in-the-loop acceptance is intentionally outside the agent's scope but the agent has all needed actions to complete and hand off.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Resources