Willow

Pros: one place for all my mcps.

Cons: codex usage is a bit finiky and not always working

Overall: connecting one mcp and enabling what i need in the ui is very comfortable

Pros: I use it to connect Claude Code, Cursor and Codex to a lot of our internal tools: logs, a database, CI, docs, feature flags, Google Workspace, Slack and so on. Our infra team set it up with an easy guide, so I was using it fast.

Cons: Sometimes it needs a lot of authenticating. It's gotten better, but it still comes up.

Overall: I use it all the time for production monitoring and for designing services. The only upkeep on my side is authenticating. I'd recommend it to any company that needs an MCP gateway.

Pros: I'm a software engineer at a company with 1,000 to 5,000 employees, and I use Willow through Claude to check logs when services fail. Before, I'd open each monitor myself, and sometimes I'd find out I needed another one just to keep following the flow. Now I just ask Claude, and it's connected to Jira, Slack and a lot of our internal systems.

Cons: Nothing's missing for my use so far, I get everything out of the box.

Overall: Our platform team set it up, I was using it for real work within a few days, and there's no upkeep on my side. I'd recommend it to any org that wants to scale up its use of MCPs.

I got a thank-you for writing this review.

Pros: Setup took me about 2 minutes and I didn’t need help from anyone. I pulled quotes, counts by month, country and account type, and the trend over time, out of 2,538 quotes. Going through that by hand just wasn’t realistic.

Cons: Nothing got in my way in what I used. But I only used it on one project as an end user, with the connection already set up, so I can’t speak to admin work or upkeep.

Overall: I’m in customer care at a 1000+ company and used Willow for an internal research assignment. I needed to build a case around one product issue fast, with real numbers and real user quotes behind it, and it got me to that data on my own without waiting on anyone. Good fit if you need a quick quantitative picture of a problem and quotes to back it up.

Pros: I’m a mobile developer at a company of about 5,000 people. I use Willow with Jira, GitHub, Slack, Sentry, Babel and Grafana. What I like most is how much faster I find error logs and work out how to fix them. When my service was crashing I used the Grafana MCP and it got me to the fix really quickly. Day to day I also go from a Sentry crash to the code in GitHub to a Jira ticket, search and post in Slack, check PRs and builds, and add translation keys in Babel. Setup was simple. IT connected it for us, then I connected and started using it.

Cons: Re-authing. I have to reconnect every week and it’s annoying. I’d like to auth everything once and be done with it.

Overall: Debugging used to take me a lot longer. Now I get to Grafana, Sentry, GitHub and Jira through Willow, so finding logs and getting to a fix is much quicker. Everyone in our company uses it, and I think any developer would benefit from it. I received a thank-you for writing this review.

Pros: We use Willow to connect Claude and Cursor to Snowflake and Trino. I use the Trino MCP all the time in my day to day work, for querying tables and updating them. Recently I used it to debug an error in an ETL for one of our most important prod tables. Setup took under an hour. My company put together a guide with the settings we needed and the whole team did it together.

Cons: Willow provides valuable governance and safety. It could be even better with clearer explanations when actions are blocked, suggested safe alternatives, and a simple approval process. This would help users move faster while keeping strong controls.

Overall: I'm a data engineer at a 1000+ person company. Willow saves me time and makes my life easier. I'd recommend it to data engineers and teams working with multiple data sources who want to use AI agents securely.

Pros: - Connecting a new MCP is automatic now, where before it was a manual pain
- Faster to get a new MCP working than before
- Works with Claude Code across GitHub, Jira, Slack and our internal MCPs
- Nothing for me to maintain, our security team handles it
- Holds up at our size, around 2,000 people in R&D with a lot of MCPs

Cons: - Nothing so far, it just works
- I can't speak to the admin side, security handles all of that
- Maybe not a fit for someone who isn't very technical

Overall: I'm a software developer at a company of about 4,000, and around 2,000 of us are in R&D, so we have a lot of MCPs. We use Willow for MCP authentication so we can control
our AI agents, and I use it with Claude Code for GitHub, Jira, Slack and our internal MCPs. Connecting a new MCP used to be a manual pain, and now it's automatic and
faster. Our security and platform teams set it up and handle the upkeep, so there's nothing for me to maintain. I'd tell my colleagues to use it, but maybe not someone who
isn't very technical. One limitation of this review: I can only speak to the developer side, since security handles all the admin.

Pros: I set it up myself in about 10 minutes.
It connects Claude to Slack, Google Docs and our CC data.
I can search my own Slack messages from Claude instead of scrolling by hand.
There’s nothing to maintain week to week.

Cons: No WhatsApp. I wanted it and it’s still missing, so teams that mostly work in WhatsApp won’t get much from it yet.

Overall: I’m a BA in Customer Care at Wix, a company of 5,000+, and I use Willow to connect Claude to Slack, Google Docs and our CC data. I set it up myself in about 10 minutes. The part I use most is searching my own Slack messages from Claude, so I don’t scroll through Slack by hand anymore. Week to week there’s nothing to maintain. One limitation: there’s no WhatsApp, which I wanted and it’s still missing, so teams that mostly work in WhatsApp won’t get much from it yet.

Pros: - One login for all our MCPs. Before, I had to do everything manually and it was a nightmare.
- It controls who gets access to which MCP, so I don't have to manage that myself.
- Our security team set it up in a couple of weeks.
- Barely any upkeep. Requesting access each day is the only thing I do.

Cons: - I have to request access every day. It's a small hassle.

Overall: I'm a software developer at a 4,000-person company, and we use Willow with mcp-s for MCP authentication. It controls who gets access to which MCP and handles the logins. Before, I had to do everything manually and it was a nightmare, and now it's one login. Our security team set it up in a couple of weeks. The only upkeep is requesting access each day, which is a small hassle. I'd recommend it to all my colleagues.

I received a thank-you for writing this review.

Pros: - Setup took minutes.
- The mcp-s CLI functions let us write general skills without knowing which MCPs a user has installed, or which versions.
- It connects to all my skills and agents, including Claude Code and our automated agents.
- I use it to debug our AB test process, ask data questions, and send Slack messages.
- Fixes take most of my upkeep time, and Willow helps with those.

Cons: - The UI. It's hard to see the tools of each MCP, and hard to understand what any of them does.

Overall: I'm a data scientist at a large company. Willow makes everything much faster and easier. I'd recommend it to any company with more than a handful of teams, where each team builds workflows, skills and MCPs that could help the others. Once you have more than a handful of MCPs and relevant skills, this is the place. I received a gift for writing this review.

Pros: Trino, Grafana, Jira, Slack, octocode and our internal systems all go through it, so for research and bug investigations I never leave the chat. When a Grafana alert came in on Slack, I read it, pulled the Grafana data and went through Trino and the code in the same chat. I added it to my MCP config and it worked out of the box.

Cons: Having to re-authenticate at all. It's only once a week, but I'd still rather not. Granted, this is probably my company's policy, unrelated to Willow.

Overall: I'm an AI engineer at a company of about 5k, and Willow is the gateway I use for all my MCPs from Claude Code and n8n. Admin is next to zero: I re-authenticate once a week and sometimes turn MCP servers on or off in the dashboard. If your company has a lot of integrations, it's worth it for pretty much any role.

Pros: Willow connects to Kiwi, where I write, and to Monday. I ask it to pull task details from Monday and draft an article in Kiwi. I used to do a lot of this by hand, and now skills I created run it faster. My biggest skill tabifies articles for 2 emulators that run together. An admin set it up, and I was using it almost right away. The one limitation is that the skills need maintaining, which the other writers and our admin do.

Cons: The one limitation is that the skills need maintaining, which the other writers and our admin do

Overall: I’m a knowledge base writer at a company with 1000+ people. I connect Willow to different skills, where I write, and to Monday. I ask it to pull task details from Monday and draft an article in our writing platform. I used to do a lot of this by hand, and now skills I created run it faster. My biggest skill tabifies articles for 2 emulators that run together. An admin set it up, and I was using it almost right away. The one limitation is that the skills need maintaining, which the other writers and our admin do.

Pros: Setup was self-explanatory and took me a matter of minutes, I connected everything myself. I use it to connect Claude to our internal analytics tools, our translation key tool, Figma, GitHub and Monday.com. The best part is having Claude analyze a Monday conversation and write me a draft instead of going through the thread manually, which has saved me hours. I can also get at our analytics data just by asking in chat.

Cons: There’s quite a bit in there I don’t use at all, so I think there’s a learning curve for a layman to get the most out of it. The connections I don’t use often also need a refresh when I come back to them.

Overall: I’m a marketing content strategist at a 1,000+ person company, and Willow is how I get Claude working with the tools I already use. I’d recommend it to anyone who wants to connect tools to their AI platform without having to deal with the manual, technical details. I received a thank-you for writing this review.

Pros: Setup took me a few minutes, and I did it on my own. I use it from my IDE to pull data from tools like Grafana and Jira, and that works really well. For one analysis I needed a lot of Grafana data and had no table for it, and I had access in seconds with no blockers. By my guess, doing it with my own tokens and API setup would have taken a few days. Upkeep is basically nothing.

Cons: Tool search could be better. I’d also like a faster overview of each MCP.

Overall: I’m a business analyst at a company of about 4K employees. I’d recommend Willow to anyone who uses LLMs at work and needs constant data from external tools.

Pros: I connect my MCPs through Willow and built a toolkit with the ones I need for my work, like Trino, Slack, Drive and a few more. I attached that toolkit to the project I work in, so I don’t have to turn specific MCPs on and off every time. I can add or switch off MCPs inside the toolkit. I set it up myself in a few days.

Cons: It would help if Willow showed me which MCPs I barely use and suggested turning them off to keep things light. It could also spot groups of MCPs I use together and suggest toolkits per task.

Overall: I’m a product manager at Wix. I connect my MCPs through Willow and put the ones I need into a single toolkit, which I attached to my project. I no longer turn specific MCPs on and off each time. I set it up alone in a few days, and upkeep is a visit once or twice a week to toggle things, or to reconnect, which takes a second. One thing I’d like: Willow should show which MCPs I rarely use and suggest turning them off, or suggest toolkits per task. I’d recommend it to anyone who uses MCPs daily. I received a BuyMe voucher as a thank-you for this review.

Pros: Setup was basically instant, and it rolled out to the whole company. It gives us secure connections through MCP, and we use it every day.

Cons: Updating the extension is manual. I do it about once a week. It’s a small chore, but it’s the one thing that annoys me.

Overall: Secure MCP connections that were up and running almost instantly.

Review: I’m an AI Builder at Wix (5K+ employees). Setup was basically instant and it rolled out company-wide. We use it every day to connect Gmail, Monday and Power BI securely. It also let us add tools that weren’t possible through Claude alone. The one downside is that updating the extension is manual, about once a week. It fits big enterprise companies best, and I’d say it’s not that relevant for small ones.

Pros: -I work in customer support at a company with 1000+ people. I connected Willow to Slack, Jira and UserVoice and use it for data analysis and tasks. It pulled my UserVoice feedback, connected the data, and gave me a summary and insights on a complex problem. It’s been running with no upkeep. I’d recommend it to analysts, and I can’t think of who I’d steer away from it.

Cons: -Setup took me a moment to figure out. I’ve also only used it for a week, so I can’t say much about the long run.

Overall: I work in customer support at a company with 1000+ people. I connected Willow to Slack, Jira and UserVoice and use it for data analysis and tasks. It pulled my UserVoice feedback, connected the data, and gave me a summary and insights on a complex problem. It’s been running with no upkeep. Setup took me a moment to figure out, and I’ve only used it for a week. I’d recommend it to analysts, and I can’t think of who I’d steer away from it.

Pros: I use it to connect my agent to Trino and run ad hoc queries. I used to run them manually. Now they go through the MCP and I don’t leave the agent. Setup took hours, not days.

Cons: Nothing so far. Haven’t hit anything that bugged me yet.

Overall: I’m a data engineer at a company in the 501-5000 range, and I use Willow to connect my agent to Trino for ad hoc queries. I used to run those manually. Now I run them through the MCP without leaving the agent. Setup took hours, not days. Nothing’s bugged me so far. If you’re on a data team and want to query from your agent, it’s worth a look.

Pros: It's the gateway that exposes our internal MCP servers to Claude Code: Grafana logs and metrics, Trino SQL on our data lake, Jira, GitHub and our build tooling. One OAuth per integration and it stays signed in. The agent runs the query and reads the result itself, so I stopped copying things between tabs. Most of my production debugging on billing issues runs through it now.

Cons: Session reliability inside the client. A server sometimes never finishes connecting at startup and I get zero tools from it, or it reports "needs authentication" after a reconnect when the token is still valid. Tool names must carry the integration prefix or you get "Integration not found", and responses come back as JSON nested inside JSON.

re auth required often but that makes sense

Overall: I'm a backend developer on a billing team at Wix. Willow is how our internal observability and data tools reach Claude Code, and since it went in most of my root-cause investigations run end to end from the agent while I review what it found. Setup on my side was just signing in to each integration. The weak spot is day-to-day connection stability, which I've worked around by calling the gateway directly with the stored token. Clearer errors and smoother reconnects would fix most of my complaints. I received a gift voucher as a thank-you for this review.

Pros: - Huge collection of mcps that is updated frequently
- Almost frictionless setup
- Friendly interface for humans and full agent friendly

Cons: - Re-auth can be annoying, usually once a day but sometimes there are hick ups

Overall: I’m a software engineer at a 1000+ company and I use Willow to connect Slack, Jira, Grafana and some internal MCPs. Before Willow I connected them all manually. Once IT approved it, Claude did a short setup for me and that was it. During one incident, Claude used the Grafana MCP through Willow to read our metrics and helped pinpoint the issue. For me and my team it was a huge time saving, as things like this would take us a full day before.