The Missive MCP connector routes your AI agent's tool calls to Missive's own MCP server through Scalekit. Each user signs in to Missive once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 20 tools.
- Tools
- 20
- What they doRead · write · destructive
- 13 · 1 · 613 read1 write6 destructive
- Users sign in with
- OAuth
- OAuth app
- Your own Missive MCP server app
Setup
Install the SDK
Terminal window npm install @scalekit-sdk/node dotenvTerminal window pip install scalekit-sdk-python python-dotenvSet your credentials
Add your Scalekit credentials to your
.envfile. Find values in app.scalekit.com > Developers > API Credentials..env SCALEKIT_ENVIRONMENT_URL=<your-environment-url>SCALEKIT_CLIENT_ID=<your-client-id>SCALEKIT_CLIENT_SECRET=<your-client-secret>Create the Missive MCP connection
In AgentKit > Connections, create a Missive MCP connection and copy its redirect URI. The name you give it is the
connection_nameyour code passes. See Configure connections.Register an OAuth app
Missive MCP server connections use your own OAuth app. Register one with Missive MCP server and add the redirect URI you copied.
Then enter the app's Client ID and Client Secret on the Missive MCP connection.
Authorize a user and make your first call
quickstart.mts import { ScalekitClient } from '@scalekit-sdk/node'import 'dotenv/config'import { createInterface } from 'node:readline/promises'const scalekit = new ScalekitClient(process.env.SCALEKIT_ENVIRONMENT_URL,process.env.SCALEKIT_CLIENT_ID,process.env.SCALEKIT_CLIENT_SECRET,)const actions = scalekit.actionsconst connector = 'missivemcp'const identifier = 'user_123'// Generate an authorization link for the userconst { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })console.log('Authorize Missive MCP:', link)const rl = createInterface({ input: process.stdin, output: process.stdout })await rl.question('Press Enter after authorizing...')rl.close()// Make your first callconst result = await actions.executeTool({connector,identifier,toolName: 'missivemcp_get_contact_details',toolInput: {},})console.log(result)Terminal window npx tsx quickstart.mtsquickstart.py import osfrom scalekit import ScalekitClientfrom dotenv import load_dotenvload_dotenv()scalekit_client = ScalekitClient(env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),client_id=os.getenv("SCALEKIT_CLIENT_ID"),client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),)actions = scalekit_client.actionsconnection_name = "missivemcp"identifier = "user_123"# Generate an authorization link for the userlink_response = actions.get_authorization_link(connection_name=connection_name,identifier=identifier,)print("Authorize Missive MCP:", link_response.link)input("Press Enter after authorizing...")# Make your first callresult = actions.execute_tool(tool_input={},tool_name="missivemcp_get_contact_details",connection_name=connection_name,identifier=identifier,)print(result)Terminal window python quickstart.pyEach user signs in once. See Authorize a user for the full flow and statuses.
Tools
Pass the exact name toexecute_toolmissivemcp_get_calendar_eventsFetch calendar events to check the user's availability.Read-onlyGet Calendar Events
Fetch calendar events to check the user's availability. Use this tool when: - The conversation involves scheduling, meetings, or availability; - Someone asks about meeting times or when the user is free; - Drafting a reply that proposes meeting times; If calendar_ids is omitted, queries all accessible calendars. Use mode='availability' to get just busy time slots, or mode='full' for event details. IMPORTANT: When inferring dates from conversation context: - If a month is mentioned without a year, use the NEXT occurrence of that month (future, not past); - "Upcoming", "next", or future-tense language always means a date after today; - Check the current date before making assumptions about which year.
Inputs
end_datestringrequired- End date in YYYY-MM-DD format
start_datestringrequired- Start date in YYYY-MM-DD format
calendar_idsarray- Array of calendar UUIDs to query. Omit to query all accessible calendars.
modestring- 'full' (default) returns event details, 'availability' returns only busy time slots
querystring- Search query string (full mode only)
missivemcp_get_contact_detailsLook up contact details from contact books.Read-onlyGet Contact Details
Look up contact details from contact books. Search by email, phone number, or general query (name, company, etc.). Returns up to 5 matching contacts.
Inputs
emailstring- Exact email address
phone_numberstring- Phone number (digits only, e.g. 4187171866)
querystring- Name, company name, or any keyword to search
missivemcp_get_conversation_entriesFetch older entries for a conversation that was cropped.Read-onlyGet Conversation Entries
Fetch older entries for a conversation that was cropped. Only call this when `next_entries_before` is present and you need more history.
Inputs
beforestringrequired- Pass the `next_entries_before` value from a cropped conversation to fetch older entries
conversation_idstringrequired- Conversation ID to fetch entries for
include_attachmentsboolean- Include file attachments for each message, internal comment and post. Supported attachments are provided as files directly; oversized or unsupported attachments include metadata and a temporary download URL only.
missivemcp_get_conversationsFetch conversations by conversation IDs or shared label IDs.Read-onlyGet Conversations
Fetch conversations by conversation IDs or shared label IDs. Only use this if you don't have a search term, otherwise use `search_conversations` to get the conversation IDs first. One of `conversation_ids`, `shared_label_ids`, `team_ids`, `email_account_ids`, or `generic_account_ids` is required. <conversation> headers and metadata are always included. Always assess first whether you need the full content or only the headers and metadata, and pass `include_content` accordingly. If you're asked to get a conversation in a specific mailbox, always use `mailbox_id` parameter. `total_count` and `unseen_count` reflect the number of conversations on all pages. If you need file attachments to get the context, reload the conversation with `include_attachments` parameter.
Inputs
include_contentbooleanrequired- Fetch full content. Pass `false` if you know you only need headers and metadata.
afterstring- Only fetch conversations modified after this timestamp
beforestring- Only fetch conversations modified before this timestamp
conversation_idsarray- Array of conversation IDs to fetch (max 25)
cursorstring- Cursor to fetch conversations after. If `cursor` is provided, all parameters except `limit` and `include_content` and `include_attachments` are ignored and are repeated from the previous request.
email_account_idsarray- Filter by email account IDs.
generic_account_idsarray- Filter by generic account IDs.
include_attachmentsboolean- Include file attachments for each message, internal comment and post. Supported attachments are provided as files directly; oversized or unsupported attachments include metadata and a temporary download URL only.
limitinteger- Maximum number of conversations to fetch, max and default is 25
mailbox_idstring- Filter by mailbox ID. Only pass the ID from the mailbox record, otherwise use `search_mailboxes` tool first. For a team inbox, pass the mailbox ID from the team record.
shared_label_idsarray- Retrieve conversations with any of the specified shared label IDs (max 100). Only pass IDs from shared label records, otherwise use `search_shared_labels` tool first. For an email label (a mailbox ID that starts with `label-`), use `mailbox_id` instead.
team_idsarray- Retrieve conversations assigned to any of the specified team IDs.
unseenboolean- Set to `true` to only fetch unseen.
missivemcp_get_search_resultsPoll for additional results from a previously started conversation search.Read-onlyGet Search Results
Poll for additional results from a previously started conversation search. Use this after search_conversations returns partial results (done="false"). Pass the search_id from the previous response.
Inputs
search_idstringrequired- UUID from previous search_conversations call
missivemcp_list_calendarsList all calendars the user has access to.Read-onlyList Calendars
List all calendars the user has access to. Returns calendar names, IDs, and ownership status (owned vs delegated/shared). Use this to discover which calendars to query for events.
Inputs
This tool takes no inputs.
missivemcp_list_organizationsList the organizations the user is a member of.Read-onlyList Organizations
List the organizations the user is a member of.
Inputs
This tool takes no inputs.
missivemcp_search_conversationsSearch conversations across all connected accounts (email, chat, etc.).Read-onlySearch Conversations
Search conversations across all connected accounts (email, chat, etc.). NEVER use this tool if the user didn't provide a search term string, use `get_conversations` instead. Supports filtering by email filters, internal/external scopes, and shared labels. If you need then to get full conversation content, use `get_conversations` with the conversation IDs. CRITICAL: This is KEYWORD search, NOT semantic search. Multi-word queries require ALL words to appear in the email - this usually FAILS. QUERY STRATEGY: 1. Extract the CORE searchable noun from the user's request 2. IGNORE qualifiers: "my", "last", "recent", "the", "about", "for" - these hurt the search 3. Use FILTERS (date, email) to narrow - not more keywords 4. If no/wrong results, expand to SYNONYMS (see below) SYNONYM EXPANSION - Start with most likely term, expand if no/wrong results: - invoice → receipt → bill → statement - quote → estimate → proposal → pricing - shipping → delivery → tracking → shipment - contract → agreement → terms - payment → paid → transaction → charge - order → purchase → confirmation EXAMPLES - User request → Correct approach: "Find my last utility invoice" → Start: query: "invoice" + since filter → No/wrong results? Try "bill", then "statement" "What was the contractor's quote?" → Start: query: "quote" → No/wrong results? Try "estimate", then "proposal" WRONG: query: "last utility invoice" (0 results - emails don't contain "last") RIGHT: query: "invoice" + filters → no/wrong results → try "bill" → try "statement" AVAILABLE FILTERS: - `email`: Conversations involving this address (sender OR recipient) - `from`/`to`: Specific email header fields - `since`/`before`: Date range (YYYY-MM-DD) - `has_attachments`: Only with attachments - `search_in_internal`: Search comments/posts/drafts only - `search_in_external`: Search emails/messages only - `mailbox_id`: Search conversations in the specified mailbox. Only pass the mailbox ID from the mailbox or team record, otherwise use `search_mailboxes` tool first. If you're asked to get a conversation in a specific mailbox, always use this parameter. Note: A conversation can have both internal comments AND external emails/messages. WORKFLOW: 1. Search with most likely term + filters 2. If done="false" → call get_search_results with search_id for more results 3. If too many results → add email/date filters 4. If no/wrong results → try next synonym from the list above 5. Once you have results → use get_conversations to fetch full content If you're unsure about filters, ASK the user for clarification rather than running a broad search. A narrow search that misses some results is better than a broad search that returns thousands. ASYNC BEHAVIOR: Search runs across multiple sources (Gmail, Office365, etc.). Initial results return quickly, but if done="false", call get_search_results with the returned search_id to get additional results as they arrive.
Inputs
querystringrequired- Search query string
beforestring- Only before this date (YYYY-MM-DD)
emailstring- Filter to conversations involving this email address
email_account_idsarray- Search in the specified email account IDs.
fromarray- Search email FROM header (provider API search)
generic_account_idsarray- Search in the specified generic account IDs.
has_attachmentsboolean- Search only with attachments
mailbox_idstring- Search in the specified mailbox. Only pass the ID from the mailbox record, otherwise use `search_mailboxes` tool first
search_in_externalboolean- Search only in emails/messages (customer content)
search_in_internalboolean- Search only in comments/posts/drafts (team content)
shared_label_idsarray- Search with any of the specified shared label IDs.
sincestring- Only after this date (YYYY-MM-DD)
team_idsarray- Search in any of the specified team IDs.
toarray- Search email TO header (provider API search)
unseenboolean- Set to `true` to only fetch unseen.
missivemcp_search_mailboxesSearch unified and label mailboxes.Read-onlySearch Mailboxes
Search unified and label mailboxes. It does not search conversations within these mailboxes, only mailboxes themselves. Does not return individual team mailboxes, retrieve them through a team record if needed. One of `query` or `types` is required. When `query` is provided, `types` is forced to "label" (to search only non-system folders). If you need to find an email account, use the `email_account_query` parameter with `types: ['all']`
Inputs
email_account_idsarray- Search mailboxes in the specified email account IDs
email_account_querystring- Search mailboxes in the specified email account by username
limitinteger- Maximum number of labels to retrieve. From 1 to 100
only_my_accountsboolean- Only return mailboxes from the user's own email accounts
querystring- Search query string
typesarray- Retrieve mailboxes by type. One of: ["inbox", "archive", "flagged", "drafts", "sent", "trash", "junk", "drafts_by_me", "sent_by_me", "send_later", "commented", "closed", "snoozed", "pinned", "assigned", "assigned_to_others", "unassigned", "all", "team_unassigned"].
missivemcp_search_responsesSearch canned responses by semantic similarity.Read-onlySearch Responses
Search canned responses by semantic similarity. Use this to find relevant templates, policies, or pre-written replies that can help answer a question.
Inputs
querystringrequired- Search query describing what kind of response you need (e.g., 'refund policy', 'shipping information')
missivemcp_search_teamsSearch teams across all user organizations.Read-onlySearch Teams
Search teams across all user organizations. At least one of `query`, `team_ids`, or `organization_ids` is required.
Inputs
any_teamboolean- All teams combined. If provided, other parameters are ignored. Shortcut for `query=*`
limitinteger- Maximum number of teams to retrieve. From 1 to 100
organization_idsarray- Array of organization IDs to search in
querystring- Search query string
team_idsarray- Retrieve teams by ID
missivemcp_search_usersSearch members of the user's organizations by name or email, or retrieve them by ID, e.g.Read-onlySearch Users
Search members of the user's organizations by name or email, or retrieve them by ID, e.g. to find assignees. The user making the request is marked with `current_user`. At least one of `query`, `user_ids`, `organization_ids` or `current_user` is required.
Inputs
current_userboolean- Pass true to retrieve the user making the request ("me"). Can't be combined with other filters
limitinteger- Maximum number of users to retrieve. From 1 to 100
organization_idsarray- Only retrieve members of these organizations, from `list_organizations`
querystring- Name or email to search for
user_idsarray- Retrieve users by ID
missivemcp_create_postPost an internal note in a conversation, e.g.WriteCreate Post
Post an internal note in a conversation, e.g. to leave context or a request for teammates. The note is only visible to users with access to the conversation, it is never sent to external recipients. If you have multiple conversations to post in, do a separate tool call for each conversation.
Inputs
conversation_idstringrequired- The ID of the conversation to post the note in
markdownstringrequired- The note content, in Markdown. Images are not supported and are shown as links
missivemcp_change_labelsAdd and or remove labels from a conversation.DestructiveChange Labels
Add and or remove labels from a conversation. At least one of `add_shared_label_ids`, `add_mailbox_ids`, `remove_shared_label_ids`, or `remove_mailbox_ids` is required. If you have multiple labels/mailboxes to add, do it all in a single tool call. If you have multiple conversations to change labels on, do a separate tool call for each conversation. Don't describe the labels in text.
- Idempotent
Inputs
conversation_idstringrequired- The ID of the conversation to change labels on
add_mailbox_idsarray- The IDs of the email label mailboxes to add to the conversation
add_shared_label_idsarray- The IDs of the shared labels to add to the conversation
remove_mailbox_idsarray- The IDs of the email label mailboxes to remove from the conversation.
remove_shared_label_idsarray- The IDs of the shared labels to remove from the conversation
missivemcp_compose_draftCreate or update a message draft.DestructiveCompose Draft
Create or update a message draft. Follow it with `deliver_draft` (using the returned conversation_id and draft_id) if the user asked to send, not just to draft. For email, unless the user's preferences specify otherwise: - Include a greeting like 'Hi [Name],' at the start; - Omit closings and signatures (the signature is appended automatically).
Inputs
modestringrequired- The operation to run. Each mode requires a fixed set of parameters: - new_conversation: start a new conversation; `type` sets the channel. type `email` requires `to`, `subject`, `body`. A phone provider type (whatsapp, twilio, twilio_whatsapp, signalwire, quo, dialpad) requires `to` (the recipient phone number) and `body`. - reply: reply to a message in a conversation. Requires `conversation_id`, `reply_to_id`, `body`. - new_message_in_conversation: a new, non-reply message in an existing conversation; Requires `conversation_id` and the same fields as for new_conversation. - update: change an existing draft. Requires `conversation_id`, `draft_id`, and at least one field to change.one of
new_conversationreplynew_message_in_conversationupdate bccarray- Recipient email addresses (BCC). On update, omit to keep the existing recipients or pass an empty array to clear them.
bodystring- The message body in plain text or Markdown. Do NOT use HTML tags. Required except an update that doesn't change the body. For email, by default include a greeting and omit closings/signatures (appended automatically); the user's preferences take precedence.
ccarray- Recipient email addresses (CC). On update, omit to keep the existing recipients or pass an empty array to clear them.
conversation_idstring- The conversation to draft in. Required for reply, new_message_in_conversation, and update.
draft_idstring- update mode: the existing draft to change.
fromstring- Who to send from. Defaults to the user's default sending account.
reply_allboolean- reply mode: include all TO and CC recipients from the message. If omitted, falls back to the user's reply-all default preference.
reply_to_idstring- reply mode: The message to reply to, ID comes from the conversation content.
subjectstring- Email subject line. Required for a new email conversation.
toarray- Recipients (To). Email message: email addresses; SMS/WhatsApp: single phone number. Required for new_conversation and new_message_in_conversation. Optional for reply (overrides the derived recipients) and update (omit to keep the current recipients; email accepts an empty array to clear them).
typestring- New message type for new_conversation and new_message_in_conversation modes. Ignored by reply and update.one of
emailwhatsapptwiliotwilio_whatsappsignalwirequodialpad
missivemcp_deliver_draftDeliver a draft in the current conversation.DestructiveDeliver Draft
Deliver a draft in the current conversation.
Inputs
conversation_idstringrequired- The ID of the conversation the draft belongs to
draft_idstringrequired- The ID of the draft to deliver, from a conversation message ID or a draft creation tool response
missivemcp_manage_calendar_eventsCreate, update, or delete a calendar event.DestructiveManage Calendar Events
Create, update, or delete a calendar event. Use list_calendars first to discover which calendars the user has access to. Use get_calendar_events to find existing event IDs for update or delete operations. Times must be in ISO 8601 format (e.g., 2024-03-15T10:00:00). For all-day events, use date format YYYY-MM-DD. Add a video call if the user might mean it. If the video conference was created, return the link to the user.
Inputs
actionstringrequired- No description.one of
createupdatedelete all_daybooleanrequired- Whether this is an all-day event (boolean)
calendar_idstringrequired- The UUID of the calendar to operate on. If you don't know the calendar UUID, use list_calendars first.
ends_atstringrequired- End time in ISO 8601 format, or YYYY-MM-DD for all-day events. Don't convert timezones, just provide the time and the `timezone` param.
starts_atstringrequired- Start time in ISO 8601 format, or YYYY-MM-DD for all-day events. Don't convert timezones, just provide the time and the `timezone` param.
timezonestringrequired- Timezone for the event (e.g., 'America/New_York').
titlestringrequired- The title/summary of the event
attendeesarray- Array of attendee objects. Pass empty array to remove all attendees. On update, only provide attendees array if you want to change, or empty array to remove all attendees.
descriptionstring- The description/body of the event
event_idstring- The provider event ID. Required for update and delete. If you don't know the event ID, fetch the event first.
locationstring- The location of the event
remindersarray- Array of reminder objects with minutes before the event start. Pass empty array to remove all reminders. Google calendars support multiple reminders; Microsoft calendars use only the first reminder. On update, only provide reminders array if you want to change, or empty array to remove all reminders.
video_conferenceboolean- Whether to attach a video conference link: Google Meet for Google calendars, Microsoft Teams for Microsoft calendars. On update: omit to keep unchanged, pass true to add, or false to remove. For Microsoft calendars, false is a no-op because online meetings cannot be removed from existing events.
missivemcp_manage_tasksCreate a task in a conversation, or update a task's title, description, assignees, team, due date or state.DestructiveManage Tasks
Create a task in a conversation, or update a task's title, description, assignees, team, due date or state. Find task IDs with `get_conversations`, user IDs with `search_users` and team IDs with `search_teams`. Assignees and teams require a conversation that belongs to an organization. Do a separate tool call for each task.
Inputs
actionstringrequired- No description.one of
createupdate conversation_idstringrequired- The ID of the conversation the task belongs to
add_assigneesarray- The user IDs to assign the task to
descriptionstring- The task description
due_atstring- The due date, in ISO 8601 format in the user's timezone (e.g., 2024-03-15T09:00:00)
remove_assigneesarray- The user IDs to unassign from the task. Update only
statestring- The new task state. Update onlyone of
todoin_progresscompleted task_idstring- The ID of the task to update. Required for update
teamstring- The ID of the team of the task
titlestring- The task title. Required for create
missivemcp_update_conversationChange a conversation's subject, color, users, assignees, team and status.DestructiveUpdate Conversation
Change a conversation's subject, color, users, assignees, team and status. All changes apply to everyone in the conversation, except `archive`, `snooze_until` and `unarchive` which only apply to the current user; snoozing also archives the conversation. Find user IDs with `search_users`, team IDs with `search_teams` and organization IDs with `list_organizations`. At least one change is required. Do all changes to a conversation in a single tool call, and a separate tool call for each conversation.
- Idempotent
Inputs
conversation_idstringrequired- The ID of the conversation to update
add_assigneesarray- The user IDs to assign to the conversation
add_usersarray- The user IDs to add to the conversation, without assigning them
archiveboolean- Pass `true` to archive the conversation for the current user
closeboolean- Pass `true` to close the conversation
colorstring- The conversation color, as a hex color code (e.g., #3b82f6)
organizationstring- The ID of the organization to move a personal conversation to. Required to add users, assignees or a team to a personal conversation
remove_assigneesarray- The user IDs to unassign from the conversation. Unassigning everyone from an open team conversation moves it to the team inbox
reopenboolean- Pass `true` to reopen the conversation
snooze_untilstring- Snooze the conversation for the current user until this time, in ISO 8601 format in the user's timezone (e.g., 2024-03-15T09:00:00)
subjectstring- The new conversation subject
teamstring- The ID of the team to move the conversation to. The conversation also goes to the team inbox and is unassigned from everyone, unless `add_assignees` or `close` is passed
unarchiveboolean- Pass `true` to move the conversation back to the current user's inbox, ending its snooze
unsnooze_on_replyboolean- Whether to unsnooze the conversation when a reply is received. Defaults to the user's setting in the app. Requires `snooze_until`
No tools match.