Every Monday, we pull back the curtain on what’s shipping in Workato Enterprise MCP.
This Week: Inbox Intelligence and Support Operations, Now Agent-Ready
Two new pre-built MCP servers are live today — Outlook Email and Zendesk Ticket Management. We now have 25 production-grade MCP servers available for Workato Enterprise MCP customers.
What’s New
Outlook Email — 18 tools
Give agents the ability to search, read, draft, and send email through Microsoft Outlook — with a draft-first sending pattern that keeps humans in control of every outbound message. Works within the authenticated user’s primary Exchange Online mailbox.
View Outlook Email documentation →
Zendesk Ticket Management — 12 tools
Let support agents and leads search and retrieve tickets, review full conversation history, manage personal and team queues, monitor SLA status, create new tickets, update fields, and add public replies or internal notes — all without navigating the Zendesk UI.
View Zendesk Ticket Management documentation →
Why This Matters
This week’s two servers close two long-requested gaps.
For Microsoft-first enterprises, Outlook Email completes the productivity loop that Outlook Calendar started. Agents can now handle the full scheduling and communication cycle — check availability, book meetings, pull prior email threads, draft follow-ups, send on approval — entirely within Microsoft 365. No switching to Gmail. No stitching together workarounds. For enterprise accounts running Microsoft infrastructure, this is the answer to “do you support M365?” The answer is now: yes, end to end.
For support teams, Zendesk Ticket Management brings agents into a governed, conversational workflow layer on top of their existing ticket operations. Support agents can surface their queue, investigate ticket history, identify SLA risk, respond to customers, and update tickets — without opening Zendesk. Team leads can triage unassigned work and catch at-risk tickets before they breach. And because the server exposes status transition timestamps and full conversation history, agents can find how similar past tickets were resolved and apply those patterns immediately.
The composability unlocks the workflows that matter most:
- Zendesk Ticket Management + Zendesk Knowledge Base (coming soon) — an agent resolves a ticket, identifies there’s no KB article covering the issue, creates a draft article from the resolution notes, and flags it for review. Support operations and knowledge management in one workflow.
- Zendesk Ticket Management + Jira — a support agent identifies a bug pattern across five tickets, creates a Jira issue from the ticket context, and links both systems — without leaving the agent conversation.
- Zendesk Ticket Management + Slack — at the start of every shift, the agent pulls their queue, surfaces any SLA-at-risk tickets, and posts a triage summary to the team Slack channel. No manual status checks.
- Outlook Email + Outlook Calendar + Salesforce — before a customer call, the agent retrieves recent email threads, pulls the calendar event, and surfaces deal context from Salesforce. Full account prep in one conversation, entirely in the Microsoft ecosystem.
Two servers. Two enterprise workflows unlocked. Both composable with the 23 servers already in production.
Real-World Use Cases
Outlook Email: For Sales, CS, and Anyone Who Lives in Their Inbox
- Deal prep: “Pull all emails with Meridian from the last two weeks. Flag anything with pricing or timeline in it.”
- Follow-up drafting: “Draft a follow-up to the thread with Acme — reference the proposal we discussed and ask for a decision by Friday.”
- Inbox triage: “Find any unread emails from customers marked high importance. Star them and summarize what each needs.”
- Meeting prep: “Retrieve my last three email conversations with Sarah Chen before my call with her at 2pm.”
- Commitment tracking: “Search my sent folder for anything where I promised a timeline or deliverable. Summarize what I committed to.”
- Thread resets: “Pull the full email thread with the Vertex team and summarize where we left off — it’s been three weeks.”
Outlook Email uses a draft-first sending pattern — agents create and update drafts, but send_draft is always a separate, explicit step. No email goes out without the user’s intent. All operations execute under the authenticated user’s own Exchange Online identity via Microsoft Graph API v1.0. Shared and delegated mailboxes are excluded in v1.
Zendesk Ticket Management: For Support Agents, Leads, and On-Call Teams
- Queue review: “What’s in my queue right now? Summarize the top three by priority.”
- Ticket investigation: “Pull ticket 8821. What’s the current status, who’s the requester, and show me the full conversation history.”
- SLA triage: “Which tickets in my group are overdue or about to breach SLA?”
- Similar ticket research: “Search for tickets about SSO timeout errors. How have we resolved this before?”
- Unassigned ticket triage: “What tickets are sitting unassigned right now? Filter for high priority.”
- Customer reply: “Add a public reply to ticket 8821 — let the customer know we’ve escalated and expect a resolution by EOD.”
- Internal note: “Add an internal note to ticket 9042 — flag that the API rate limit error recurs on Monday mornings, likely a batch job.”
- Resolution timing: “When was ticket 7741 solved? I want to know how long it sat in open before someone picked it up.”
Zendesk Ticket Management is scoped to Zendesk Support’s core ticketing module. Knowledge base management is handled by a separate Zendesk Knowledge Base MCP Server. Tag updates replace the entire tag set on a ticket — the LLM must retrieve current tags via get_ticket before modifying them to avoid unintentionally removing existing tags. SLA monitoring requires SLA policies to be configured in the underlying Zendesk account.
What Makes These Enterprise-Ready
- Verified User Access: Both servers execute under the authenticated end-user’s identity. Email actions are attributed to the sending user. Ticket updates, replies, and notes are attributed to the acting agent. No shared service accounts, no attribution gaps.
- Draft-first and confirm-before-write patterns: Outlook Email enforces create_draft → send_draft. Zendesk Ticket Management requires get_ticket before status changes and tag updates. Both servers put humans in the review loop before irreversible actions.
- Permission inheritance: Outlook Email respects Exchange Online delegated permission boundaries. Zendesk Ticket Management enforces Zendesk role-based visibility — agents only see tickets their account grants them access to. Neither server elevates privileges.
- Managed infrastructure: Workato hosts, scales, and maintains both servers. No API versions to track, no pagination logic to maintain, no infrastructure to provision.
- Composable: Outlook Email chains with Outlook Calendar, Salesforce, Gong, and OneDrive. Zendesk Ticket Management chains with Jira, Slack, Confluence, and the forthcoming Zendesk Knowledge Base server.
- Audit trails: Every tool call logged with full context — who, what, when, and what was returned.
Get Started
Both servers are available now for Workato customers with Enterprise MCP.
Install time: Minutes
Custom development: None
Deployment complexity: One-click activation
View Outlook Email documentation →
View Zendesk Ticket Management documentation →
The bottom line: Other vendors are still announcing MCP roadmaps. We’re shipping production-ready servers every Monday.
See you next Monday.