Skip to main content
Glama

Related Servers

Alternatives to FIREFIGHTER

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for renting real GPUs from the terminal. Enables browsing, renting, chatting, managing, and pooling GPU instances with per-second billing, designed for AI agents.
      158 npm
      1
      -
    • A
      license
      B
      quality
      D
      maintenance
      agent-mq is a message queue that enables AI coding agents to communicate with each other across sessions and machines. Agents can send messages, delegate tasks, and coordinate work — all through MCP tools. Supports Claude Code, Cursor, Codex, OpenClaw, and any MCP-compatible tool. UUID-based authentication with per-user data isolation. Self-hostable with Docker.
      7
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted MCP server that lets coding agents such as Claude Code, Codex, OpenCode and Antigravity join named rooms, exchange messages, and run writer/reviewer loops without copying text between terminals. Long-poll hooks wake agents when a reply arrives (no tokens spent while waiting), and a web UI lets a human watch rooms and pause, resume or close them.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to delegate scoped tasks across multiple providers like Codex, Claude Code, and Antigravity through a single local MCP server, with quota monitoring, notifications, and remote control via messaging apps.
      13
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that connects AI coding agents (Claude Code, Codex, Cursor, etc.) on the same machine via a shared message bus, enabling them to chat, delegate tasks, and collaborate privately without cloud or internet.
      73 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool covers a distinct phase of the job lifecycle: submit queues work, wait blocks for completion, status reports the machine, job mutates an existing job, and plan announces future intent. The only mild overlaps are wait vs. status (both surface job state) and status's pricing mode vs. submit, but the descriptions make the boundaries clear enough.

    Naming Consistency4/5

    All tools share a consistent firefighter_ prefix, giving a predictable namespace. The suffixes mix verbs (submit, wait) with nouns (status, job, plan), so the pattern isn't a pure verb_noun scheme, but it is readable and internally coherent.

    Tool Count5/5

    Five tools is well-scoped for a shared-machine job queue: submit, wait, inspect, modify, and plan. Each tool maps to a real user need with no filler.

    Completeness4/5

    The surface covers the full lifecycle: queue, poll, inspect, mutate (extend/tier/cancel), and pre-announce plans. Minor gaps exist—no explicit way to list your own jobs or fetch full logs on demand (logs surface only via wait's tail), but agents can work around this with status and repeated waits.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues