Skip to main content
Glama
bababoi-bibilabu

Agent-MQ

by bababoi-bibilabu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Agent-MQ

  • Message MCP

    gimjin
    A
    license
    A
    quality
    C
    maintenance
    Real-time push notifications and alert sounds free you from staring at the screen. While the AI works, you can comfortably enjoy a cup of coffee.
    1
    10 npm
    9
    TypeScript
    MIT

Related Servers

  • agent-bus-mcp

    MustaphaSteph
    A
    license
    Not graded
    quality
    D
    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.
    54 npm
    18
    MIT

  • aichat-mcp

    Wayy-Research
    A
    license
    A
    quality
    D
    maintenance
    MCP server for inter-agent communication. Gives multiple Claude Code sessions a shared message board, agent registry, and orchestration layer — backed by a cloud relay so agents can coordinate across machines, repos, and teams.
    8
    45 npm
    MIT

  • backchannel

    unison-labs-ai
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server for async messaging between AI coding agents, enabling cross-harness and cross-machine communication with Slack-like semantics and mail-shaped delivery.
    2
    MIT

  • bearier-mcp

    kumabear917
    F
    license
    Not graded
    quality
    C
    maintenance
    Bearier MCP lets two desktop AI agents collaborate asynchronously through a shared local task queue — no API keys, no IDE, no cloud. Just one SQLite file bridging agents that otherwise can't talk to each other.
    1
    -
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

B3.3/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity: mq_add adds agents, mq_history views history, mq_login handles authentication, mq_logout disconnects, mq_ls lists agents, mq_recv consumes messages, and mq_send sends messages. The actions and targets are well-defined and non-overlapping.

Naming Consistency5/5

All tool names follow a consistent 'mq_' prefix with descriptive suffixes in snake_case (e.g., mq_add, mq_history, mq_login). This pattern is uniform across all seven tools, making them predictable and easy to identify as part of the same server.

Tool Count5/5

With 7 tools, the count is well-scoped for a message queue server, covering core operations like agent management (add, list), message handling (send, receive), authentication (login, logout), and history viewing. Each tool earns its place without redundancy or bloat.

Completeness4/5

The tool set provides comprehensive coverage for basic message queue operations, including agent lifecycle, messaging, and authentication. A minor gap exists in lacking tools for advanced features like message prioritization or queue configuration, but core workflows are fully supported without dead ends.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources