InterAgentMail
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INTERAGENTMAIL_HOME | No | Override the default data directory for mailbox storage. Defaults to %LOCALAPPDATA%\InterAgentMail on Windows or ~/.local/share/interagentmail on macOS/Linux. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| iam_whoamiA | Return the mailbox identity bound to this MCP server. |
| iam_list_mailboxesA | List known IAM mailbox addresses and display names. |
| iam_inboxC | List newest inbox messages for this project without marking them read. |
| iam_readA | Read one inbox message by full id or unique prefix. |
| iam_sendB | Send a new message. Priority is normal or urgent; urgent may steer an active Codex turn. |
| iam_replyB | Send a substantive reply in an existing thread, preserving originator and routing. |
| iam_archiveC | Archive one fully handled inbox message. |
| iam_timer_setB | Set a one-shot reminder for this mailbox at an ISO-8601 timezone-aware time. |
| iam_timer_set_teamB | Schedule independent timers for an authorized team. Only an explicitly granted active leader may use this. |
| iam_timer_set_forA | Schedule a timer for one authorized teammate; explicit timer.schedule permission is required. |
| iam_timer_listB | List this mailbox's outstanding temporary reminders. |
| iam_timer_clearA | Clear a handled timer permanently. Cleared timers are not archived. |
| iam_timer_cancelB | Cancel an outstanding timer created by or targeted to this mailbox. |
| iam_timer_snoozeA | Move one outstanding timer to a new ISO-8601 timezone-aware due time. |
| iam_team_add_memberA | Add one mailbox to this leader's team when team.manage_members was explicitly granted. |
| iam_team_remove_memberA | Remove a non-leader mailbox from this leader's team when team.manage_members was granted. |
| iam_list_channelsA | List known IAM public and private chat channel names. |
| iam_chat_tailC | Read recent chat messages, enforcing private-channel membership. |
| iam_chat_joinA | Join one live channel and make it active; joining another leaves the prior one. Use channel_type=private and with_agent only to create a new DM. |
| iam_chat_leaveA | Leave this mailbox's active live chat channel and stop its supervisor notifications. |
| iam_chat_subscriptionsA | Return this mailbox's active live chat subscription, if any. |
| iam_chat_postA | Post to this mailbox's active chat channel. Join a channel first; its channel cannot be supplied here. |
| iam_chat_seenC | Mark recent chat messages as seen by this project. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| identity_resource | The identity and project root bound to this server. |
| inbox_resource | The current inbox without read-state side effects. |
TDQS
Scored across 23 tools
Most tools map to a distinct resource+action, but timer_clear vs timer_cancel and the timer_set_team/timer_set_for/timer_set trio could cause selection hesitation. Descriptions generally resolve the ambiguity.
All tools share the iam_ prefix and snake_case convention, and most follow verb_noun. A few noun-style names like iam_inbox and compound names like iam_timer_set_for break the strict pattern slightly.
23 tools is on the heavy side for an MCP server, though each domain cluster (mail, chat, timers, team) is internally coherent. The count feels manageable but exceeds the typical well-scoped range.
Mail, chat, timer, and team management all have core lifecycle coverage: send/read/reply/archive, join/post/tail/leave, set/list/cancel/snooze, and add/remove member. Minor gaps like team listing or message search exist but are not blocking.