Skip to main content
Glama
Sign In
codex-intercom-mcp

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
      D
      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
      1
      MIT

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

      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.
      5
      116 npm
      1
      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

    Disambiguation4/5

    Most tools have clearly distinct purposes: join/team for team management, send/ask/reply for messaging, list/whoami for discovery, and set_summary for status publishing. There is some overlap between intercom_status (shows unread messages/pending asks) and intercom_pending (reads unread inbound messages/asks), and intercom_list vs intercom_team could be momentarily confused, though descriptions clarify the boundaries.

    Naming Consistency4/5

    All tools share a consistent `intercom_` prefix and lowercase snake_case, making them recognizable as a family. However, styles vary between bare verbs/nouns (`send`, `ask`, `team`, `status`, `pending`, `whoami`) and a verb_noun form (`set_summary`), so it is not a perfectly uniform pattern.

    Tool Count5/5

    Ten tools is well within the ideal 3–15 range for a session-messaging and team-coordination server. Each tool maps to a meaningful operation (join, list, send, ask, reply, pending, status, team, summary, whoami) with no obvious padding.

    Completeness4/5

    The surface covers the core lifecycle: identity, session discovery, team creation/inspection, direct messaging, ask/reply, reading pending items, and publishing summaries. Minor gaps exist—no explicit leave-team/unregister operation and no way to retrieve historical messages beyond unread/pending, but agents can work around these.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data

    Resources