Skip to main content
Glama
Sign In
Agent-MQ

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
    15 npm
    9
    TypeScript
    MIT

Related Servers

  • agent-bus-mcp

    MustaphaSteph
    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.
    58 npm
    MIT

  • Agent Rooms

    alisheraxmedov
    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

  • Commons

    Neoo-Blue
    A
    license
    B
    quality
    A
    maintenance
    Lets multiple AI agents and parallel coding sessions share one memory and task ledger, so they can claim work instead of duplicating it, resume each other's handoffs and reasoning, and use credentials without ever seeing the keys. Connects assistants such as Claude Code, Codex, Cursor, Gemini, ChatGPT and custom agents over MCP, backed by a single local SQLite file or a self-hosted Postgres hub.
    35
    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
    35 npm
    MIT
Deploy Server
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

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
ResponsivenessSyncing

Resources