claude-intercom-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAUDE_INTERCOM_NAME | No | Optional name for this session | |
| CLAUDE_INTERCOM_MODEL | No | Optional model name (e.g., opus, sonnet) | |
| CLAUDE_INTERCOM_SESSION_ID | No | Optional session ID |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| intercom_whoamiA | Return this Claude session's intercom identity for reliable targeting. |
| intercom_statusA | Show intercom connection status, active sessions, unread messages, and pending asks. |
| intercom_listB | List intercom-connected Pi or Claude sessions on this machine. |
| intercom_set_summaryA | Publish a short status summary so other sessions can discover what this Claude session is doing. |
| intercom_sendB | Send a non-blocking direct message to another intercom session by name, full ID, or unique ID prefix. |
| intercom_askB | Ask another intercom session a question and wait for its reply. |
| intercom_pendingB | Read unread inbound messages and unresolved asks for this Claude session. |
| intercom_replyB | Reply to a pending inbound ask. If exactly one ask is pending, to/reply_to can be omitted. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: asking questions, listing sessions, checking pending messages, replying, sending DMs, setting summaries, checking status, and identifying oneself. No overlap or ambiguity.
All tools share the 'intercom_' prefix with descriptive verbs or nouns. While some use plain verbs (ask, list, reply, send) and others use state nouns (pending, status, whoami) or verb_noun (set_summary), the pattern is predictable and clear.
8 tools is ideal for the domain of inter-session communication. Each tool serves a necessary function without redundancy, covering sending, receiving, discovery, and status.
The tool set covers all essential operations for inter-session messaging: sending (both blocking and non-blocking), reading, replying, discovering sessions, displaying status, and self-identification. No obvious gaps like broadcast or notification are needed for basic communication.