Skip to main content
Glama
gitByEOS

agents-chat-mcp

by gitByEOS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to agents-chat-mcp

No user-submitted related servers found.

    Related Servers

    • Agent Bridge

      chaojixiaoyezi
      F
      license
      B
      quality
      B
      maintenance
      MCP server that bridges multiple AI agents for unified local chat, supporting private messages, chat rooms, role queues, and broadcast with fixed identities and rate limiting.
      14
      1
      -

    • spiderswitch

      hiddenpath
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables agents to dynamically switch between multiple AI models (OpenAI, Anthropic, Google, etc.) with unified protocol-driven configuration and capability discovery.
      Apache 2.0

    • agent-bridge

      itcomduke
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP central server that lets multiple AI agents (e.g., Claude Code, kimi-code) exchange private messages, shared channel broadcasts, and unified message streams via MCP tools, with SQLite persistence and per-connection identity binding.
      15 npm
      MIT
    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.1/5.0

    Scored across 4 tools

    Disambiguation3/5

    The register, send, and watch tools have clear distinct purposes. However, agent_chat_helper is a vague 'multi-purpose' tool with no specific scope, potentially overlapping with the others.

    Naming Consistency5/5

    All tools follow a consistent 'agent_chat_<verb>' pattern (except 'helper' which is a noun, but it still adheres to the prefix and is understandable).

    Tool Count5/5

    Four tools is appropriate for a basic chat agent server, covering registration, sending, and watching for messages without unnecessary bloat.

    Completeness3/5

    The core messaging workflow is covered, but missing obvious operations like unregistering, listing agents, or leaving the chat room, which may hinder agent workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources