Every Monday, we pull back the curtain on what’s shipping in Workato Enterprise MCP.
This Week
Two new additions to the catalog — Trello and GitLab Explorer. The catalog now stands at 50 production-ready pre-built MCP servers.
What’s New
Trello — 9 tools
Manage tasks without touching the Trello interface. An agent can discover boards and lists, find and filter cards by assignee or due date, read full card details including checklists, create and move cards, post comments, and tick checklist items complete.
View Trello MCP Server Documentation →
GitLab Explorer — 15 tools
GitLab is where software ships. The GitLab Explorer MCP Server gives agents the developer’s-eye view across project and repository context, issues, merge requests, commit history, cross-project search, and pipeline status. It can also create and update issues, open merge requests from existing branches, and add notes.
View GitLab Explorer MCP Server Documentation →
Why This Matters
Trello and GitLab are the live surfaces where work is moving, where a card gets dragged across a board or a merge request waits on a green pipeline. They’re also where the small interruptions pile up. Checking what’s assigned to you, moving a card, seeing why a pipeline failed, opening an issue from something that just came up in conversation. Each one means stopping what you’re doing and switching into another tool.
These two MCP servers cut down on context switching. For example, a project gets broken into tasks on Trello and built and reviewed in GitLab, and now an agent can reach into both instead of just reasoning about them from the outside. It can pull your overdue cards before a standup, then check which merge requests are blocked on a failing pipeline, without you touching either interface.
And because both run on Workato Enterprise MCP, the reach doesn’t stop at one tool. A flurry of Slack messages can become a tracked card in the right Trello list. A failing pipeline in GitLab can become a Jira issue. They compose with every other server already in the catalog.
Real-World Use Cases
Trello
For individual contributors and team leads getting a board ready before a standup.
- “What’s assigned to me and due this week across my boards?”
- “Take these five action items and create them as cards in the Sprint Backlog list.”
- “Move the ‘API rate limiting’ card to In Progress and add a comment that I’ve started on it.”
- “Show me everything overdue on the Marketing board, oldest first.”
Design notes: The card-move and update tools follow a resolve-before-write pattern. This means board and list IDs are confirmed before any change, preventing cards from landing in the wrong place. Batch card creation previews the full set before anything is written.
GitLab Explorer
For engineers and engineering managers keeping an eye on what’s shipping.
- “Give me the status of the payments-service project before standup — open MRs and anything with a failing pipeline.”
- “Why did the pipeline on MR 412 fail? Show me the failed jobs.”
- “Open a merge request from the feature/checkout-v2 branch into main and title it ‘Checkout redesign.'”
- “Create an issue: ‘Login throttling triggers on valid retries’, and assign it to me.”
Design notes: The server reads pipeline status but never runs CI/CD, pushes code, or merges — those actions stay with a person. Write operations confirm before they run, so issues aren’t closed and merge requests aren’t opened silently. Current issue state is retrieved before any label or assignee update, so existing values are never dropped.
What Makes These Enterprise Ready
Across these two servers, a few patterns are worth naming explicitly.
- Verified user access: Every tool call executes under the authenticated user’s own identity, through delegated OAuth across both servers. Cards, comments, issues, and merge requests are attributed to the acting user. No shared service accounts, no attribution gaps.
- Permission inheritance: Agents can only see and change what the user’s own role already allows. The servers never elevate privileges or expose restricted boards, cards, files, or projects.
- Bounded by design: The irreversible actions stay with people. GitLab never runs CI/CD, pushes code, or merges.
- Read-before-write: ID-dependent operations read current state first. Trello resolves list IDs before moving a card and GitLab retrieves current issue and MR state before updating labels or assignees.
- Confirmation before write: Trello requires approval before every write and previews a full card batch before creating; GitLab confirms before creating an issue or merge request or closing an issue.
- Managed infrastructure: Workato hosts, scales, and maintains both servers. No API versions to track, no rate limits to manage, no infrastructure to provision.
- Composable: Chains with Slack, Jira, OneDrive, Google Drive, Salesforce, GitHub, and the rest of the catalog for workflows that span planning, tracking, communicating, and shipping.
- Audit trails: Every tool call logged with full context — who, what, when, and what was returned.
Get Started
Trello and GitLab Explorer are available now for Workato customers with Enterprise MCP.
Install time: Minutes
Custom development: None
Deployment complexity: One-click activation
View Trello MCP Server Documentation →
View GitLab Explorer MCP Server Documentation →
View the full catalog — now 50 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 Monday.
See you next Monday.