Willow

Pros: Claude Code agents use it for Jira: creating tickets, assigning them, moving them into sprints and commenting.
Posting to Slack through MCP-S, because the claude.ai Slack connector stamps attribution on messages.
Creating and publishing Babel translation keys.
Grafana logs and metrics during on-call.
Running several agents in parallel that each report through Jira, so the gateway sits in the middle of your daily workflow.

Cons: Jira comments through MCP-S are plain text only: no @mentions or formatting.
The @mcp-s/cli wasn't authenticated, so you had to use the MCP tools instead.
It's sometimes still "connecting" at session start (it was today).

Overall: One login gets my AI agents into Jira, Slack, Grafana and our internal tools.

I use Willow every day to connect Claude Code agents to the systems my team works in. The agents handle Jira tickets and sprints, post to Slack, add translation keys and query logs, all through one gateway with one login. I can run several agents at once and they report progress on their own. [Specific win.] One honest limitation: some integrations are thinner than the real API, for example Jira comments are plain text only and some board endpoints are missing.

Pros: - All my MCPs go through it: Trino, Slack, Gmail and our internal ones
- I can install plugins through it
- My agents use mcp-s-cli a lot and it works
- I was using it for real work on the first day
- It mostly just runs, with almost no upkeep

Cons: - I have to log in about once a week. Nothing big so far.

Overall: Willow is the base of how I connect MCPs to my agents and I use it every day. I was up and running on the first day and it mostly just runs. Without it I can't work. I'd recommend it to any professional who uses agents and needs to connect and govern them.

Pros: I’m an IR engineer and I use Willow to work with several of our security systems like Upwind, plus Jira, Google Drive, Sheets and Slides. Building an incident response timeline used to take me hours of designing the sheet, copy pasting logs and fixing columns. Now I give the logs to Claude with the Google Sheets MCP through Willow and get a timeline in 5 minutes. Setup was a copy paste command per MCP server, about 10 seconds.

Cons: The MCP server names were slightly different than I expected.

Overall: We have 100+ MCP servers at our company, all under Willow, and it makes using all of them really easy. I use it to create and update docs, IR reports and presentations in Google Slides. The only upkeep is a daily Okta SSO login to each MCP server, and it really takes about 10 seconds. I’d recommend it to anyone who wants to work with a lot of MCP servers.

Pros: I use the Willow CLI to work with MCPs from Claude Code and Codex. The best part is I don’t have to set up the MCPs again in every coding agent. Authentication when I hit an MCP is quick and easy too. Getting the CLI running took me about a minute, and I never touch it after that. No weekly upkeep at all. Honestly it changed my life.

Cons: Agents don’t use the Willow CLI by default. I set it in my personal settings so MCP tasks go to Willow, but I still sometimes have to mention it in my prompt.

Overall: I’m in Data Engineering Infra at Wix (1,000+ employees). Before Willow, every coding agent needed its own MCP setup and its own auth. Now I set it up once through the CLI and use it from both Claude Code and Codex. I’d recommend it to any tech or non-tech company that has to integrate with lots of different MCPs.

Pros: Connected all the MCPs I use daily (Trino, Slack, Jira, Google Workspace, Event Snitch) with help from the Willow team
Used it from day one, every day
Saved time on a real task: on-call shifts in everyone's calendar in a few minutes instead of about an hour
Almost no upkeepDoesn't proactively suggest more integrations, so I only use what I already know about

Cons: Doesn't proactively suggest more integrations, so I only use what I already know about

Overall: I'm an analyst at a company with 1,000+ people, and I use Willow every day with Trino, Slack, Jira, Google Workspace and Event Snitch, all connected with help from the Willow team. Once I had to update our team's on-call rotation, so I connected the email and Slack MCPs and got everyone's shifts into their calendars, based on the constraints people had posted in Slack. It took a few minutes instead of about an hour. There's almost no upkeep. The one limit is that Willow doesn't proactively suggest more integrations, so I only use what I already know about. I'd recommend it to anyone working with Claude Code and Cursor.

I received a thank-you for writing this review.

Pros: We use MCP-S for our internal company MCPs at Wix. It was already part of the company infra, so getting started locally was instant. Just entered the URL and the MCP was connected

Cons: I need to re-login each time, though that might be a company policy and not an actual infrastructure issue

Overall: As an R&D Manager at Wix, I use MCP-S to connect to all of my company MCPs. It was already part of the company infra, so local usage was instant, just entering the URL in my agent configuration and that's it. In the past, finding the right MCP was a journey, and we didn't have proper indexing. Now I do it through Willow.

Pros: As an analyst I use Willow every day, mostly without noticing it's there. My Claude Code skills go through it to get to SQL analysis, python coding, knowledge bases and document, my Google suite and slack. All on one login. I don't have to set up each tool on my own.

Cons: The first call of a new session always opens a browser to log in, and that gets old.

Overall: For me it's just the layer between my agent and our data, and it stays out of the way. It's a good fit for a company with lots of internal tools that wants AI agents working across them.

Pros: Connects me to all our MCPs in one go, in a few seconds
Saves me time, so I can get on with my work faster
Hands off after setup, with no admin work from me

Cons: A few times I had to log in more than once in a day, like it didn't remember I was already logged in

Overall: It mostly saves me time. I'd recommend it to any company that needs to connect to a lot of MCPs at once. I can't think of who I wouldn't recommend it to.

Pros: I'm in security and most of my day to day work runs through MCPs. The two I use most through Willow are Okta and Splunk. I pull a user's Okta groups and recent logins, and I run Splunk searches without opening Splunk. Setup was quick, IT helped me with it. It usually just works

Cons: Willow access is sometimes down. I also have to re-auth the MCPs from time to time. That's about it

Overall: The best example was onboarding a new user who needed a set of Okta groups. Through Willow I checked which groups they were missing and filed the add requests. Before that it was clicking through Okta admin one group at a time. I'd recommend it to everyone

Pros: Willow excels at proactive runtime guardrails, enforcing least-privilege permissions and real-time auditability directly at the tool-execution layer. It allows teams to safely connect autonomous agents and MCP gateways to enterprise data in days rather than waiting weeks for custom security wrappers and manual reviews.

Cons: Frequent re-authentication prompts interrupt active developer sessions, and routing calls through live runtime checks adds slight evaluation latency.

Overall: Willow provides a vital security layer for scaling autonomous agents in an enterprise environment. It successfully bridges the gap between fast-paced developer adoption and strict compliance standards by securing tool execution in real time, making the minor authentication friction well worth the trade-off.

Pros: I use Willow to connect to a lot of the tools and MCPs we have at work, and to authenticate on a few of them quickly. My team sent me a link and I was using it right away. It was easy and straightforward. The best part is I skip the annoying stuff, like connecting to MCPs and logging in again and again.

Cons: Honestly I haven’t hit a real problem with it so far, so I don’t have a specific complaint to share.

Overall: I’m a junior software engineer at a company of about 4,000 people. Willow does one job for me. It takes the pain out of connecting to our tools and MCPs. I don’t do any admin or upkeep on it, so I can’t speak to that side. I’d recommend it to anyone who connects AI to their tools, which is pretty much everyone.

Pros: Setting up took me minutes, and I did it with Claude. Every AI client we use works with it, and using our internal MCPs through Claude feels about 10x faster for my day to day work. There’s basically nothing to maintain week to week.

Cons: The one thing I’d improve is figuring out which internal MCPs exist and what each one actually does.

Overall: I’m a software dev at Wix, and all our internal MCPs for Wix’s dev tools go through Willow, company wide. I’d recommend it to any friend working as a software dev in tech.