Every Monday, we pull back the curtain on what’s shipping in Workato Enterprise MCP.
This Week
Two new servers join the catalog: a WordPress Content Operations server for managing posts, pages, and comments, and a Google Slides server for building and editing presentations. That brings the catalog to 60 production-ready servers.
What’s New
WordPress Content Operations — 27 tools
Covers the full content lifecycle on self-hosted WordPress and WordPress.com: create and update posts and pages, organize with categories and tags, manage media metadata, and moderate or reply to comments. It’s schema-aware for custom post types like press releases or case studies, and it deliberately excludes analytics, reporting, and site administration, which stay out of scope for a different server.
View WordPress documentation →
Google Slides — 17 tools
Handles everything that happens inside a presentation: searching and summarizing decks, adding or reordering slides, updating text and speaker notes, and managing review comments. Creating a new file or copying a template is intentionally left to Google Drive; this server picks up once the file exists.
View Google Slides documentation →
Why This Matters
Neither of these servers tries to do everything. WordPress handles content, not the dashboard, plugins, or traffic reports. Google Slides handles what’s inside a deck, not file creation or where it lives in Drive. That’s not a limitation, it’s the point: a server that tries to cover an entire application ends up doing most of it poorly, and an agent that has to guess which tool owns which task ends up doing the wrong thing confidently.
The WordPress server backs this up with get_post_type_schema, which tells an agent exactly what fields a press release or case study post type expects before create_post ever runs. That matters more in an enterprise WordPress environment than it sounds: custom post types are how these sites structure everything beyond a basic blog post, and getting a field wrong means a case study that doesn’t render like the rest.
Google Slides draws its line at the file boundary. It doesn’t create presentations or manage where they live in Drive; it opens once a presentation already exists and handles the structure and content from there. Split the work that way, and each server can go deep instead of shallow: WordPress knows what a custom post type needs, Slides knows what a placeholder expects, and neither has to also be a mediocre file manager.
Composability Pairings
Google Slides + Google Drive: copy a template deck in Drive, then use Slides to populate placeholders, add slides, and generate speaker notes for the finished version.
WordPress + Canva: autofill a branded graphic for a new case study, then attach it as the featured image when creating the WordPress post.
WordPress + Slack: draft a new press release as a custom post type, then post a preview to a review channel before it goes live.
Real-World Use Cases
WordPress for the comms team publishing a press release under deadline.
- “What’s the schema for our press release post type?”
- “Create a new press release using this content and today’s date.”
- “List all draft press releases waiting for review.”
- “Reply to this comment and mark it as approved.”
Design notes:
get_post_type_schema runs before create_post or update_post on a custom post type, so structured fields get filled in correctly instead of guessed. trash_post and trash_comment move items to trash rather than deleting them outright, and the server has no access to site settings, plugins, or analytics, those live elsewhere.
Google Slides for the exec assistant polishing a board deck the night before.
- “Summarize the key points across my Q3 board deck.”
- “Add a two-column slide after slide 5.”
- “Replace every instance of ‘Q3’ with ‘Q4’ across the deck.”
- “Generate speaker notes for slide 10.”
Design notes:
get_slide_elements identifies the specific element on a slide before update_text_content edits it, so the right text box gets changed. delete_slide won’t remove the last remaining slide in a presentation. Creating the deck itself is Drive’s job; this server takes over once the file exists.
What Makes These Enterprise-Ready
Verified User Access: All tool calls execute under the authenticated user’s own WordPress or Google identity. Posts, comments, and slide edits are attributed to the acting user.
Managed infrastructure: Workato hosts, scales, and maintains both servers. No API versions to track, no rate limits to manage, no infrastructure to provision.
Schema-aware structured content: WordPress’s get_post_type_schema ensures custom post types like press releases and case studies get correctly structured data, not a best guess.
Clear scope boundaries: WordPress stays out of analytics, reporting, and admin; Google Slides leaves file creation to Drive. Each server owns a defined slice of the workflow instead of duplicating what a sibling server already handles.
Composable: Chains with Canva, Google Drive, Slack, and the rest of the catalog for workflows that span content, design, and review.
Audit trails: Every tool call is logged with full context: who, what, when, and what was returned.
Get Started
WordPress Content Operations and Google Slides are available now for Workato customers with Enterprise MCP.
Install time: Minutes
Custom development: None
Deployment complexity: One-click activation
View the full catalog — now 60 pre-built servers.
Ready to connect your stack? Check out our self-service trial.
The bottom line: Other vendors are still announcing MCP roadmaps. We’re shipping production-ready servers every week.
See you next Monday.