For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.mcpbundles.com/bundle/missive
Skill page: https://www.mcpbundles.com/skills/missive
Tools: 32
Live probe refreshed Nov 21, 2026 · Endpoint host mcp.mcpbundles.com
AI Skill
SKILL.md
Domain knowledge for Missive — workflow patterns, data models, and gotchas for your AI agent.
Missive
Missive is a collaborative shared inbox spanning email, SMS, WhatsApp,
Instagram, Messenger, custom channels, and live chat. The data model is
built around conversations; everything else (messages, drafts, posts,
comments, tasks) lives inside a conversation.
Entity Hierarchy
Organization — top-level workspace. Most write paths require an
organization id.
Team — a sub-grouping inside an organization, with active_members
(notified) and observers (not notified). Teams own team inboxes and can
own conversations.
User — a Missive seat. The API token owner is marked me: true.
Account — a connected channel (email mailbox, SMS line, WhatsApp
number, Messenger page, custom-channel adapter, …). Account ids appear
in messages and drafts; the catalog of accounts lives in Missive's
Settings, not in a list endpoint.
Contact book → contact group / contact organization →
contact. Contact books are the entry point — contact_book id is
required for both contact_groups and contacts list calls.
Conversation — the unit of triage. Holds messages, comments, drafts,
posts, and an array of tasks.
Draft — outbound message in progress; send immediately via the
draft create path with send=true.
Post — integration / automation entry. Also the documented way to
mutate conversation state.
Shared label — cross-conversation tag, optionally nested via parent.
Canned response — reusable email template scoped to organization or
user.
Task — standalone, conversation subtask, or tasked-conversation.
Hook (webhook) — event subscription; backed by a Missive Rule under
the hood.
Workflows
Read a mailbox: list conversations with at least one of mailbox /
shared_label / team_inbox / team_closed / team_all (Missive returns
HTTP 400 'You need to paginate at least one mailbox' when all are
absent). For each conversation of interest, fetch messages, comments,
drafts, and posts via the per-conversation sub-listings. Pull the full
body of a specific message via the by-id message fetch.
Triage: use the post tool with action flags (close, reopen,
add_to_inbox, add_to_team_inbox, add_assignees, add_shared_labels,
remove_shared_labels, conversation_color, team + force_team) to mutate
state — there is no PATCH endpoint on conversations, and the API does
not expose an 'archive' parameter at all.
Reply or send: create a draft. To send immediately, set send=true.
To schedule, set send_at to a Unix epoch (mutually exclusive with
send=true). To reply to an existing conversation, pass conversation
(preferred when you have the id) or references (when matching by email
Message-ID). For correct paragraph spacing in HTML bodies, use
<div>...</div><div><br></div> instead of <p>...</p>.
Sync contacts: list contact_books, then for each book paginate
contacts (optionally with modified_since for incremental sync and
include_deleted for tombstones).
Manage canned responses: list responses for the user, optionally
filtered by organization; create/update via upsert; delete one or many
via the batch delete tool.
Webhooks for automations: subscribe with the create-webhook tool,
store the returned id, delete with the delete-webhook tool. There is
no list / get for webhooks via the API — visibility lives in
Missive's Rules settings UI.
Analytics: kick off an analytics report (organization + start + end
required), then poll for it 5 seconds later and re-poll every 5
seconds until 200. Reports expire 60 seconds after completion. Plan
gating applies (Productive plan for any report; Business plan for
team / user / label / account filters).
Gotchas
Conversation listing requires a mailbox filter. mailbox, shared_label,
team_inbox, team_closed, or team_all — at least one is mandatory. The
API's 'junked' mailbox is what the Missive UI calls 'Spam'.
Contact groups need both contact_book AND kind. Either alone gives
HTTP 400 'Required parameter missing'.
Contact updates with infos / memberships REPLACE the entire array.
Missing items are deleted by Missive. Always read the contact first if
you only intend to add one info entry.
Conversation state mutations go through posts, not through any
dedicated PATCH endpoint. There is no 'archive' parameter.
Sent messages cannot be deleted via the REST API. Only drafts have
a delete endpoint. Posts also have a delete endpoint (admin-gated for
shared conversations).
HTML bodies need <div>+<br>, not <p>, for visible paragraph
spacing in Missive's renderer.
Analytics reports are async and short-lived — 60-second expiry
after completion; expect 404 until the report is ready.
Analytics requires an organization-admin PAT for org-wide reports
(organization + start + end only). Non-admin tokens get HTTP 400 even
without filters.
Analytics filters are Business-plan only — teams, users,
shared_labels, accounts, and account_types require Missive Business;
Productive orgs must omit those parameters.
Custom-channel message creation is for INCOMING messages. To send
outbound mail or chat, use the draft tool with send=true; the
custom-channel message endpoint simulates a message arriving from an
external system, not one going out.
Webhook events sometimes look like rules in the Missive UI —
the create-webhook tool creates a Missive Rule with a webhook action;
deleting via the delete-webhook tool removes that rule.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms
Missive
Add to your AI client, then sign in once when you connect.
Missive is a collaborative inbox for teams, unifying email, SMS, WhatsApp, Instagram, Messenger, and live chat in one shared workspace with internal comments, shared drafts, assignments, shared labels, tasks, and rules. Use it to read and triage conversations, send and schedule outbound messages, manage canned responses, sync contacts, subscribe to event webhooks, and pull analytics reports.
This listing identifies a third-party integration. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
Kick off an analytics report for an organization between Unix-epoch start and end. Returns { reports: { id } }; pass that id to the analytics report fetch to retrieve the data (usually ready 2-3 seconds later, occasionally up to 30s). Plan gates: requires Productive plan; the filter parameters (teams, users, shared_labels, accounts, account_types) require a Business plan.
Missive Create Analytics Report — Kick off an analytics report for an organization between Unix-epoch start and end. Returns { reports: { id } }; pass that id to the analytics report fetch to retrieve the data (usually ready 2-3 seconds later, occasionally up to 30s). Plan gates: requires Productive plan; the filter parameters (teams, users, shared_labels, accounts, account_types) require a Business plan.
Missive Create Custom Channel Message — Inject an INCOMING message into a Missive custom channel — this simulates a message arriving from an external system Missive does not natively integrate. NOT for sending outbound email or replying to a customer; create a draft with send=true for that. Required: account (custom-channel account id). Use 'conversation' or 'references' to append to an existing conversation; otherwise a new one is created.
Missive Create Draft — Create an outbound draft. send=true sends the draft immediately; send_at=<unix epoch> schedules a later send; omitting both leaves it as a draft for a human to edit. 'conversation' or 'references' append the draft to an existing conversation; without them a new conversation is created. Body HTML: <div>...</div><div><br></div> renders with paragraph spacing in Missive; <p> tags do not. quote_previous_message=true on a reply embeds the previous message body verbatim, including content authored by
Missive Create Post — Create a post in a conversation. Posts are the API's path for changing conversation state: the close, reopen, add_to_inbox, add_to_team_inbox, add_assignees, add_shared_labels, remove_shared_labels, team+force_team, and conversation_color fields change the conversation along with writing the post body, and the post remains as a visible record of what changed. Body shape: one of text, markdown, or attachments is required, plus notification (title+body). text and markdown cap at 8000 characters; t
Missive Create Webhook — Subscribe a URL to a Missive event (incoming email/SMS/Facebook/WhatsApp/Twilio chat, or new comments). Returns { hooks: { id } } — store the id to delete later. Filters (content_contains / starts_with / ends_with, plus event-type-specific filters like is_task/author/mention for new_comment, from_eq/subject_contains for incoming_email) are all optional. Behind the scenes Missive creates a Rule with a webhook action; the rule is editable in Missive's Rules UI.
Frequently Asked Questions
What is the Missive MCP server?
Missive is a collaborative inbox for teams, unifying email, SMS, WhatsApp, Instagram, Messenger, and live chat in one shared workspace with internal comments, shared drafts, assignments, shared labels, tasks, and rules. Use it to read and triage conversations, send and schedule outbound messages, manage canned responses, sync contacts, subscribe to event webhooks, and pull analytics reports. It provides 32 tools that AI agents can use through the Model Context Protocol (MCP).
How do I connect Missive to my AI agent?
Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/missive. Authentication is handled automatically.
Missive Delete Draft — Delete a draft from a conversation. The id is the draft id returned when the draft was created (NOT the conversation id, and NOT a sent message id — sent messages have no delete endpoint in the Missive REST API).
Missive Delete Post — Delete a post from a conversation. The id is the post id returned when the post was created. For posts in conversations shared with an organization, the API token must be owned by an admin of that organization.
Missive Delete Responses — Delete one or more canned responses by id. Missive supports batch deletion via a comma-separated id path. In organizations with restricted response management (enterprise feature), only admins/owners may delete organization-scoped responses. Responses created by external integrations (e.g. WhatsApp templates) cannot be deleted through this endpoint.
Missive Delete Webhook — Delete a Missive webhook subscription by id. Behind the scenes the underlying rule with the webhook action is removed.
Missive Get Analytics Report — Fetch a previously-created analytics report by id. An empty HTTP 404 means the report is not ready yet, has expired, or never existed — Missive recommends polling 5 seconds after creation and retrying every 5 seconds until 200. Reports expire 60 seconds after completion.
Missive Get Contact Books — List contact books the authenticated user has access to. Each contact book has an id (required when creating contacts or listing contact_groups / contacts within it), a name, and sharing fields (share_with_organization / share_with_team / share_with_users). The contact_book id is the entry point to every contact-scoped operation: listing contact groups or contacts without it returns HTTP 400.
Missive Get Contact Groups — List contact groups (kind='group') or contact organizations (kind='organization') within a single contact_book. Both parameters are required by Missive — omitting either returns HTTP 400 'Required parameter missing'. Contact organizations model real businesses; contact groups model ad-hoc tag-style groupings. Group ids are referenced from contact memberships.
Missive Get Contacts — List or fetch contacts. Provide 'id' for a single contact. Otherwise list within a contact_book (required) — supports ordering by last_name (default) or last_modified, free-text search across all contact infos, modified_since for incremental sync, and include_deleted to surface tombstones. Each contact returns infos[] (email/phone/twitter/etc.) and memberships[] (group + title).
Missive Get Conversations — List or fetch conversations. Provide 'id' for a single conversation. The id is the full value from a list, including the hyphens; a short hex prefix is not an id. Otherwise list — at least one of mailbox, shared_label, team_inbox, team_closed, or team_all is required (Missive returns HTTP 400 'You need to paginate at least one mailbox' if all are absent). Conversations are ordered newest-activity first; paginate by passing the oldest row's last_activity_at as 'until'. The contact filters (email,
Missive Get Message — Fetch one message (single id) or up to several messages (comma-joined ids) by id. Returns headers, full HTML body, attachments[], and the embedded conversation summary. Inline images appear in the body HTML without a src attribute — they carry data-missive-attachment-id pointing into the attachments[] array, where the actual url is exposed.
Missive Get Organizations — List organizations the authenticated user belongs to. Returns each organization's id and name. Organization ids are required inputs to analytics reports, team creation, shared label creation, and most write paths.
Missive Get Responses — List or fetch canned responses (reusable email templates). Omit id for a paginated list filtered by organization; provide id for the full response including HTML body, subject, to/cc/bcc fields, shared_labels, and inline-image attachments. Inline images embed via data-missive-attachment-id=<attachment uuid> attributes pointing into the attachments[] array.
Missive Get Shared Labels — List shared labels visible to the authenticated user. Each label has id, name, name_with_parent_names (slash-joined path for nested labels), color, and organization. Label ids are passed to drafts/posts/messages as add_shared_labels and remove_shared_labels, and to conversation listings as shared_label.
Missive Get Tasks — List or fetch tasks (standalone, conversation-scoped subtasks, and tasked conversations). Provide id for one task in detail; otherwise filter by organization / team / assignee / state / type / parent conversation / due_at range. Listed assignees are user-id strings; the single-fetch path returns full user and team objects.
Missive Get Teams — List teams in organizations the authenticated user belongs to. Each team has id, name, organization, active_members (user ids who get team-inbox notifications), and observers (user ids who can manage the team without notifications). Team ids are inputs to drafts/posts/messages 'team' field, conversation listings with team_inbox / team_closed / team_all, and tasks with team.
Missive Get Users — List users in organizations the authenticated user is part of. Each user has id, email, name, avatar_url, and a 'me' boolean marking the API token owner. User status (availability, away, out of office) is not exposed by the Missive REST API.
Missive List Conversation Comments — List internal comments in a conversation (the team-only @mention thread). Returns body, author, mentions[], optional attachment, and an optional task object (description, state todo/in_progress/closed, due_at, assignees, team) when the comment is task-shaped.
Missive List Conversation Drafts — List draft messages in a conversation. Each draft carries the same headers + attachments shape as a message plus an author field. Create a draft to add outbound work in progress; delete a draft by its draft id to remove one from the conversation.
Missive List Conversation Messages — List messages in a conversation (drafts excluded). Each message carries headers (from/to/cc/bcc), preview, type (email, sms, whatsapp, custom, …), delivered_at, attachments[], and email Message-ID. Body HTML is fetched separately via the message-by-id fetch.
Missive List Conversation Posts — List integration / automation posts in a conversation. Posts are the trace left by integrations that close, reopen, assign, label, or otherwise mutate the conversation. Each post has a username, username_icon, optional notification, text/markdown body, and an attachments[] array of compact attachment objects.
Showing the first 25 tools — full list and schemas: Directory API.
How many tools does Missive provide?
Missive provides 32 tools that can be called by AI agents, along with a SKILL.md that gives your AI agent domain knowledge about when and how to use them.
What authentication does Missive require?
Missive uses API Key. Missive requires credentials. Connect via MCPBundles and authentication is handled automatically.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.
More in collaboration
Other MCP servers in this category from the directory index