Skip to main content
Glama
ctliz

codex-intercom-mcp

by ctliz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to codex-intercom-mcp

No user-submitted related servers found.

    Related Servers

    • agent-bus

      rishabhjava
      A
      license
      A
      quality
      B
      maintenance
      Enables multiple coding agents (Claude Code, Codex, Cursor) to discover each other's sessions, search transcripts, ask questions, and handoff tasks through a shared MCP server.
      5
      2 npm
      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
      60 npm
      MIT

    • 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
    • tincan by BrutalSystems

      tincanofficial

      BrutalSystems
      A
      license
      A
      quality
      A
      maintenance
      Enables live Claude Code and Codex sessions on the same machine to send each other text messages directly. It provides peer discovery, message sending, and a shared message log through MCP tools.
      4
      6,093 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

    A3.6/5.0

    Scored across 10 tools

    Disambiguation3/5

    Several tools surface overlapping views: intercom_status reports active sessions and unread messages/asks, which overlaps with intercom_list (sessions), intercom_team (coworkers), and intercom_pending (unread messages/asks). The descriptions clarify intended focus, but an agent could reasonably pick status vs list vs pending for the same need.

    Naming Consistency5/5

    Every tool follows a uniform intercom_<verb/noun> snake_case convention (intercom_send, intercom_reply, intercom_set_summary, intercom_whoami). The pattern is fully predictable with no style deviations.

    Tool Count5/5

    Ten tools is well-scoped for a session coordination/intercom server, covering identity, messaging, teams, and status without redundancy-driven bloat. Each tool corresponds to a distinct coordination action.

    Completeness4/5

    The surface covers the core lifecycle: join/create teams, send/ask/reply messaging, identity, status, and summaries. Minor gaps remain, such as no leave-team/leave-session operation and no message history retrieval, but agents can work around these.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources