Skip to main content
Glama
ctliz

codex-intercom-mcp

by ctliz

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CODEX_INTERCOM_NAMENoOptional intercom display name for this Codex session. Set at MCP registration time with --env CODEX_INTERCOM_NAME=planner.
PI_CODING_AGENT_DIRNoOverrides the base directory for intercom runtime files, including the broker Unix domain socket. The socket path becomes $PI_CODING_AGENT_DIR/intercom/broker.sock. Defaults to ~/.pi/agent.
CODEX_INTERCOM_MODELNoOptional model label for the session. Set at MCP registration time with --env CODEX_INTERCOM_MODEL=codex.
AGENT_INTERCOM_SCOPE_IDNoBroker-enforced scope routing via protocol v4. Defines the logical scope for session discovery and messaging. Same-scope sessions see each other; cross-scope messaging requires explicit full session ID. Not a security boundary. Defaults to no scope (global).
CODEX_INTERCOM_SESSION_IDNoOptional stable session ID for this Codex session. Set at MCP registration time with --env CODEX_INTERCOM_SESSION_ID=codex-planner.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
intercom_whoamiA

Return this Codex session's intercom identity for reliable targeting.

intercom_teamA

Show your current manager and the live coworkers owned by that manager. No arguments are required.

intercom_joinA

List, join, or create a named intercom team without tmux. Omit name to list joinable teams. Set create=true to create a team and join as manager.

intercom_statusA

Show intercom connection status, active sessions, unread messages, and pending asks.

intercom_listA

List intercom-connected Pi or Codex sessions on this machine.

intercom_set_summaryA

Publish a short status summary so other sessions can discover what this Codex session is doing.

intercom_sendA

Send a non-blocking direct message to another intercom session by name, full ID, or unique ID prefix.

intercom_askA

Ask another intercom session a question only when the next step depends on its reply. Use intercom_send for assignments, progress/status checkpoints, and notifications.

intercom_pendingC

Read unread inbound messages and unresolved asks for this Codex session.

intercom_replyA

Reply to a pending inbound ask. Use to plus which=oldest/latest when one sender has multiple unresolved asks.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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