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
      25 npm
      MIT

    • agent-bus-mcp

      MustaphaSteph
      A
      license
      Not graded
      quality
      A
      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.
      23 npm
      20
      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
      740 npm
      1
      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

    A3.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but intercom_join's 'omit name to list teams' behavior overlaps with intercom_team, and intercom_status vs intercom_pending both report unread messages/pending asks. Descriptions do clarify the primary intent, so only minor confusion is likely.

    Naming Consistency5/5

    All tools use a uniform intercom_<action> snake_case pattern, making the set highly predictable. The only slight deviation is noun-like action names (intercom_status, intercom_pending), but the convention remains consistent.

    Tool Count5/5

    Ten tools is well-scoped for an inter-session messaging and team management server. Each tool maps to a distinct capability (identity, discovery, messaging, status) without obvious filler.

    Completeness4/5

    Core workflows are covered: identity, discovery, team join/inspect, send/ask/reply, pending reads, and status summaries. Minor gaps exist, such as no leave/disband team operation or team-wide broadcast, but agents can work around these by sending to individual members.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources