MCP server for autoMessage — gives Claude, Codex, and any MCP client the ability to send iMessages, read conversation history, manage drafts, and resolve contacts via the autoMessage REST API.
Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
AUTOMESSAGE_API_KEYAPI keyrequiredYour autoMessage API key, from the dashboard at go.automessage.app. Use a read-only key to expose history without send access.
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
send_imessageNo description publishedThis tool published no description. Forge does not invent one.
list_conversationsFind the user's iMessage conversations, ordered by most recently active. Each has a GUID you pass to other tools. To find conversations with a phone number, use `participant` (matches 1:1 AND group chats; loosely-formatted numbers are normalized). Use `name` to search by contact/group name. Pass at…Find the user's iMessage conversations, ordered by most recently active. Each has a GUID you pass to other tools. To find conversations with a phone number, use `participant` (matches 1:1 AND group chats; loosely-formatted numbers are normalized). Use `name` to search by contact/group name. Pass at…
No input schema was published for this tool.
get_conversation_historyReturn the message history of a single conversation, ordered newest first. Useful for catching up on a thread, summarizing, or extracting context before drafting a reply.Return the message history of a single conversation, ordered newest first. Useful for catching up on a thread, summarizing, or extracting context before drafting a reply.
No input schema was published for this tool.
list_recent_messagesMost recent messages ACROSS ALL conversations, newest first — ideal for "catch me up" or "what did I miss today". Filter by direction and time window; paginate with cursor.Most recent messages ACROSS ALL conversations, newest first — ideal for "catch me up" or "what did I miss today". Filter by direction and time window; paginate with cursor.
No input schema was published for this tool.
list_draftsList outbound drafts. Useful for checking what's queued for the Mac agent, what is held by the new-outreach limit, what was recently sent, or what failed. By default returns drafts in any state; filter with status (preferred), or sent / send_error.List outbound drafts. Useful for checking what's queued for the Mac agent, what is held by the new-outreach limit, what was recently sent, or what failed. By default returns drafts in any state; filter with status (preferred), or sent / send_error.
No input schema was published for this tool.
get_draft_statusNo description publishedThis tool published no description. Forge does not invent one.
cancel_pending_draftSoft-cancel a pending draft before the Mac agent dispatches it. Only works while the draft is still `sent: false`. Once sent, this returns 409 Conflict.Soft-cancel a pending draft before the Mac agent dispatches it. Only works while the draft is still `sent: false`. Once sent, this returns 409 Conflict.
No input schema was published for this tool.
list_contactsList the user's saved iMessage contacts. Contacts are auto-populated by the Mac agent from macOS Contacts as the user messages people, plus any manual additions. Useful for resolving "Sarah" to a phone number before sending.List the user's saved iMessage contacts. Contacts are auto-populated by the Mac agent from macOS Contacts as the user messages people, plus any manual additions. Useful for resolving "Sarah" to a phone number before sending.
No input schema was published for this tool.
find_contactSearch the user's contacts by display name, phone, or email. Returns the closest matches by case-insensitive substring. Use this when the user references someone by name to resolve them to a sendable phone/email handle.Search the user's contacts by display name, phone, or email. Returns the closest matches by case-insensitive substring. Use this when the user references someone by name to resolve them to a sendable phone/email handle.
No input schema was published for this tool.
create_contactCreate or upsert a contact. Use when the user asks to "save" a new person to their address book. Requires at least one of phone_number or email. Note: this is a one-way edit — changes here do not propagate to the user's native macOS/iOS Contacts.Create or upsert a contact. Use when the user asks to "save" a new person to their address book. Requires at least one of phone_number or email. Note: this is a one-way edit — changes here do not propagate to the user's native macOS/iOS Contacts.
No input schema was published for this tool.
agent_online_checkCheck whether the user's Mac agent is currently running and able to dispatch iMessages. If `online: false`, any send_imessage call will queue the draft but it won't dispatch until the Mac comes back online.Check whether the user's Mac agent is currently running and able to dispatch iMessages. If `online: false`, any send_imessage call will queue the draft but it won't dispatch until the Mac comes back online.
No input schema was published for this tool.
9 of 11 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for autoMessage — gives Claude, Codex, and any MCP client the ability to send iMessages, read conversation history, manage drafts, and resolve contacts via the autoMessage REST API.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
81 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+69 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.