Missive

@Missive show me all team members across our support and sales teams, grouped by team

Based on the Missive API response, here's what I found: **Support Team** (4 members): - Sarah Chen (sarah@company.com) - Active - Marcus Rodriguez (marcus@company.com) - Active - Aisha Patel (aisha@company.com) - Active - Tom Wilson (tom@company.com) - Away **Sales Team** (3 members): - Jennifer Lee (jlee@company.com) - Active - David Kim (dkim@company.com) - Active - Rachel Moore (rmoore@company.com) - Active This illustrative example shows how the MCP would combine data from the List Missive Teams and List Team Members tools to give you a consolidated view of your organization structure.

This example demonstrates read-only team discovery, useful for onboarding or org chart updates. Requires API key with read access to users and teams. The actual member list and status indicators depend on your Missive account configuration at query time.

@Missive draft an email to support@customer.com thanking them for their patience during our outage, mention we've implemented monitoring improvements

I've created a draft in Missive with the following details: **To:** support@customer.com **Subject:** Thank You for Your Patience During Our Service Interruption **Body:** "Thank you for your patience during yesterday's service interruption. We understand how disruptive downtime can be to your operations. Our team has implemented enhanced monitoring systems to detect and prevent similar issues in the future. We appreciate your continued partnership." **Draft ID:** msg_draft_8x4k2p9 This draft is now saved in your Missive inbox and ready for you to review, edit, or schedule for sending. The illustrative content shows how the MCP structures outbound communications.

This write operation creates a draft without sending, giving you review control before the message goes out. The MCP needs API access to create drafts in your Missive workspace. Draft content is AI-generated based on your prompt—always review before sending customer-facing communications.

@Missive generate an analytics report for all conversations in the last 30 days, then summarize response time trends and busiest hours

I've requested an analytics report from Missive covering the past 30 days. Report ID: `rpt_7h3m9k1` (processing). Once the report completes, typical insights would include: **Response Time Trends:** Average first response time has decreased from 4.2 hours to 2.8 hours over the period, indicating improved team efficiency. **Busiest Hours:** Peak conversation volume occurs between 10 AM - 12 PM EST (34% of daily messages) and 2 PM - 4 PM EST (28% of daily messages). Lowest activity is 6 PM - 8 AM EST. This illustrative summary shows how the MCP can initiate report generation and interpret the resulting data to surface actionable patterns in your team's communication workflow.

This synthesis example pairs Missive's analytics capabilities with AI reasoning to extract insights. Report generation is asynchronous—actual data depends on your conversation history. Useful for capacity planning and shift scheduling, but requires sufficient historical data for meaningful trends.

When Missive MCP wins for shift-change context sharing

A 6-person support team runs three 8-hour shifts across time zones. The outgoing shift needs to brief the incoming team on open escalations, customer sentiment, and pending replies. The Missive MCP lets your AI pull analytics reports for the last shift window, draft handoff summaries with message counts and response times, and post them to a shared conversation before shift end. The Create Analytics Report and Create Draft tools handle the heavy lifting; List Users ensures the right people get tagged. This works best when your team already lives in Missive for customer comms—if you're stitching together Slack, email, and a separate ticketing system, the context stays fragmented. If handoffs happen in Missive and you want them automated, this MCP closes the loop.

When this MCP handles batch outreach without a marketing platform

A 3-person sales team at a B2B startup sends personalized cold outreach to 20-40 prospects per week. They draft messages in a spreadsheet, then manually copy-paste into Missive throughout the day. The Missive MCP lets your AI read the spreadsheet, generate drafts with the Create Draft tool, and queue them for review before send. The team approves or tweaks each draft in Missive's UI, then schedules sends at staggered intervals. This setup works when volume is under 50 messages per day and personalization matters more than automation scale—above that threshold, you need a real email sequencing tool with deliverability monitoring. If your outreach is high-touch and Missive is already your sending layer, this MCP saves 2-3 hours of copy-paste per week.

When Missive MCP routes urgent messages to on-call engineers

A 10-person product team uses Missive for customer support, but critical bugs reported via email need immediate engineering attention. The Missive MCP creates a webhook that fires when a message contains keywords like 'production down' or 'data loss', then sends a formatted alert to the on-call Slack channel with conversation context. The Create Webhook and Send Missive Message tools handle the plumbing; List Team Members ensures the right engineer gets pulled in. This works when your escalation logic is simple (keyword-based or sender-based) and you want the routing to live in Missive rather than a separate incident management tool. If you need SLA tracking, priority queues, or multi-stage escalation, you've outgrown this approach. For straightforward 'flag and notify' workflows, this MCP keeps the team responsive without adding another platform.