Willow

Pros: I don't manage tokens or local MCP configs, and new servers just appear. It's become the default way our agents talk to internal systems.

Cons: I haven't hit a real limitation as an end user, but our platform team runs it, so I can't speak to the admin side.

Overall: I'm a software developer and use Willow with Claude Code through its CLI. One login gets my agents into 140+ MCP servers, from Slack and Grafana to AWS and our internal change-approval tools. I received a gift card as a thank-you for this review.

Pros: Gives our agents access to the tools we already use — Git, Trino, Slack, Jira, Monday, and a few others — through MCP. It was already rolled out when I started, so there was no setup on my end, and week to week it’s hands off, nothing to maintain or re-auth. Where it helps most is everyday stuff: searching Git when I’m not sure if some reference code already exists, investigating issues, and doing QA on data. Saves real time on all of that.

Cons: Honestly, I haven’t hit a real pain point with it yet. Nothing’s come up that’s been annoying or missing so far.

Overall: It solves the problem of giving agents governed access to tools we already run on, instead of connecting each one separately or doing the lookup by hand. No setup, no upkeep, and it saves time on the everyday work.

Pros: I'm a data engineer at Wix and I use Willow to connect systems like Google and Airflow. Setup took less than a day from kickoff to actual use. Once it's connected, there's basically zero upkeep week to week. The biggest help is how it handles all our MCPs when the system is under heavy load.

Cons: I'd like a way to set a preference order for the MCPs. Without it, it's a bit hard to manage them personally exactly how I want.

Overall: It solves the headache of dealing with multiple platforms at once. I connected it once and don't have to mess with it again. If you work with several systems at the same time, I'd say give it a try. We got it running on day one and it just works.

Pros: Through one MCP connection I get Jira, GitHub, Slack, Grafana and our internal tools, which makes investigations really easy. I set it up myself, it was very easy, and I install plugins through it too. I rarely have issues and the UI is very good.

Cons: in my harness I only see Willow, not which MCP servers or tools are connected behind it.

Overall: I’m a full stack developer at Wix and I use Willow with Claude and Codex. It’s very comfy and I’d recommend it to anyone.

Pros: Willow gives us one single point to connect all the MCPs we use at Wix. Our dev and debug tools, plus the MCP servers I build myself, all go through it. It’s a much simpler way to connect everything than handling each MCP on its own.

Cons: Honestly haven’t hit anything major. Our platform team set it up and they keep working on it, so if there are rough edges I don’t really see them.

Overall: I’m a backend engineer at Wix and every MCP call we make goes through Willow. Platform team set it up, I just started using it, and there’s nothing for me to maintain week to week. Having one point for all our MCPs makes things simpler. Even stuff like Grafana logs I just pull through MCP now. I’d recommend it to friends who work in the field.

Pros: It gives you the install command for every IDE, which saves a lot of time. I use it to connect Claude Code and Cursor to GitHub, Playwright, Jira and our internal MCPs. It’s also a good place to discover more MCPs.

Cons: We have to reauthenticate too often. That’s my main complaint.

Overall: Willow is rolled out company-wide where I work (around 3,000 people) and I use it as a software engineer. It’s most useful if you’ve got a lot of MCPs or a mix of IDEs.

Pros: It’s a super easy system. All my MCP connections go through it, so they aren’t tied to one AI tool. When I switched my main tool from Cursor to Claude Code, moving everything over took about 30 minutes. Adding a new connection takes a few minutes. Our infra team made an install bundle, so setup took me about an hour. I use GitHub through it every day to read, search and write across repos, Google Workspace for Sheets and Slides, and Monday to add tasks that come out of agent conversations.

Cons: Sometimes I need to re-auth, and I only find out because the calls start failing. I’d rather get an alert telling me to re-auth before that happens. Other than that I don’t have much to complain about.

Overall: A good fit for teams where lots of people use several AI tools and MCPs and IT is small.

I got an incentive for writing this review, but I honestly recommend it.

Pros: I didn't set anything up. When I started using Claude for work, it was already connected through Willow and it just worked. Once in a while there's a security step, and Claude handles it without me doing much.

Cons: I don't really know what it does or which tools go through it. That's also kind of why it's good, it stays out of my way.

Overall: I'm a data analyst in marketing at a company of around 3,000 people. I use Claude for work, and Claude uses Willow for its MCP connections. I'd point it at companies with lots of tools, a team, and the budget, so people aren't each making these connections on their own. I got a thank-you for writing this review.

Pros: I use it to connect Claude Code to all our external MCPs, mostly Slack. When I was debugging an incident, Claude Code pulled up the Slack thread where someone had already found the cause, so I didn't have to dig through Slack myself. Getting connected on my end was very quick. It also fits big companies that need security and want to see which MCPs employees are connecting to.

Cons: Sometimes I have to reconnect, but not very often.

Overall: I'm a developer at a company of about 2,000 to 3,000 people, and I use Willow to connect Claude Code to all our external MCPs. Mostly I use it to read Slack. Once while I was debugging an incident, Claude Code pulled up the Slack thread where someone had already found the cause, so I didn't have to dig through Slack myself. I wasn't part of the setup, and getting connected on my end was very quick. Sometimes I have to reconnect, but not very often. I think it makes sense for big companies that need security and want to see which MCPs their employees are connecting to.

Pros: I use Willow to connect and authenticate our MCPs for Claude Code: GitHub, Slack, Gmail, Google Drive and Databricks. Authentication is really fast. IT set it up, and once it got to me it took seconds to get working. Before this I had to configure each MCP separately in Claude Code. Re-authenticating once in a while is quick too.

Cons: Nothing so far. Admittedly I mostly see the user side, since IT handles setup, so I can’t speak to what admin looks like.

Overall: It gets all our MCPs authenticated for Claude Code in one place, so I don’t have to set each one up myself. I’m a data analyst at a company of around 4k people and I work across all of these tools from Claude Code. It’s a good fit for teams running coding agents with several MCPs, and for companies where IT controls access. My company is giving me a small thank-you for writing this review.

Pros: I'm a marketing analyst and most of my work is data analysis on Databricks. Before Willow I wrote all the SQL myself. Now I don't have to write every query by hand. Setup was very fast, I did it on my own. And there's almost no upkeep week to week.

Cons: It disconnects sometimes and I have to deal with auth again. That's the one thing I'd want fixed.

Overall: It connects to our Databricks so I can do my analysis without writing all the SQL myself. I'd recommend it to anyone who works with data. I wouldn't give it to a non-technical audience.

Pros: Connecting standard tools like GitHub, Slack, Jira, and Grafana to Cursor and Claude took about a minute. Uploading and connecting our own internal MCPs was just as easy. Once it's set up, there is almost no weekly upkeep, and it makes tasks like debugging Grafana alerts from inside my coding workflow much faster.

Cons: Having to re-auth about once every few days is annoying.

Overall: I'm a full stack dev at a ~2,000 person company using Willow to hook up MCPs to Cursor and Claude. Both built-in integrations (GitHub, Slack, Jira, Grafana) and our own custom MCPs were quick to set up and use for daily work like debugging Grafana alerts. Good fit for devs who don't want to mess with local MCP configs. I received a thank-you gift card for writing this review.

Pros: I use it every day to connect Claude Code to different MCPs. GitHub, Jira, Slack, and a bunch of internal tools. The connection is fast and stable. Our platform team set it up, so I just use it. I really like using it.

Cons: Just that I have to re-authenticate every few days.

Overall: I'm a software developer at a company with 1000+ people, and we have lots of MCPs. Willow is how I connect Claude Code to them, and it's fast and stable, which matters since I use it daily.

Pros: Setup took me about two minutes and I didn't need anyone from IT or security. I use Willow to connect the MCPs I need, like Google Workspace, Search Console, SimilarWeb and Athena, to both Cursor and Claude Code. The thing I like most is pulling Search Console and SimilarWeb data straight into a session instead of exporting files first. Upkeep week to week is close to nothing.

Cons: Nothing has bothered me so far. I've mainly used it with a few data sources, so I can't speak for everything it connects to. I'll update this if that changes.

Overall: I'm a marketing analyst at Wix. Willow is how I get data into my agent sessions without the export step, and it's the same connections in Cursor and Claude Code, so I don't set anything up twice. I'd recommend it to any team in the company, including non-technical ones.

I received a thank-you from Willow for writing this review.

Pros: I connect my AI agent to GitHub, Jira, Slack and Grafana through Willow. In GitHub it does pretty much everything: reads code, creates PRs, reviews PRs, checks issues and projects. In Jira it reads tickets and comments on them. Slack is mostly reading. In Grafana it creates dashboards and checks their status.

Cons: Nothing worth mentioning, it's working great for me :)

Overall: I work at Wix, and most of the company uses Willow. Setup was easy because Wix gave us clear instructions on how to connect everything. During a prod issue it helped me read the Slack thread, the Grafana graphs and the Jira ticket, then open a PR to fix it. I'd recommend it to anyone working with an AI harness.

Pros: It puts everything in one place. I set it up on my own to connect my MCPs. Having Trino, internal connections, and my data and testing tools accessible through one setup without needing IT for every single step is great.

Cons: I have to re-authenticate often. Other than that I’m happy with it.

Overall: I use Willow to connect my MCPs. My setup includes Trino, data and testing tools, and internal connections that feed straight into my daily tasks - like pulling context for translations. It’s much faster than searching each tool on its own, and I was able to set it up by myself. I’m happy with it overall, though having to re-authenticate often can be annoying.

Pros: I use Willow mostly through Claude to get at Jira, GitHub and Slack. Setup took minutes and I did it myself. I had a bunch of separate MCP servers hooked up and their tool lists were costing around 23K tokens on every message. On Oct 22 I turned them all off and moved to Willow’s CLI instead. Upkeep is pretty much nothing.

Cons: The SSO session expires every now and then, sometimes in the middle of a task, and I have to log in again. Not a huge deal, but it’s annoying when it happens.

Overall: Willow gives my agent access to our internal tools without paying for it in context on every message. If you’re a dev using Claude or another agent across a lot of internal tools, it’s worth it. If you only need GitHub, gh already does that. I received a thank-you for writing this review.

Pros: When someone adds a new MCP I can find it easily, which is how I found a custom Kubernetes MCP built internally. There’s no upkeep on my side

Cons: My one gripe is that installing still means copy pasting a command, I’d rather click install in the UI and have it done automatically

Overall: I’m an infra engineer at a 1000+ company and I use Willow to browse our MCPs and get install guides for them. I mainly use Codex, and I’ve pulled in MCPs like Slack, GitHub, Grafana and Kubernetes. Good for any team, a solo dev can skip it.

Pros: The setup was easy. The MCPs were already listed in Willow, so I just clicked “Use” and that was it. I didn’t need help from anyone. After that, Cursor knows how to use Willow on its own, so my day to day work with it is smooth. I use it for Airflow, databases, cron jobs and more.

Cons: It’s a small thing. Every few days I need to re-authenticate to Willow from Cursor. Before that happens, Cursor tries to reach the MCP, fails, and tells me it can’t connect unless I re-authenticate. That’s a separate step and it doesn’t happen automatically. One more prompt to Cursor fixes it, so it’s not a big deal.

Overall: It saves me a lot of time and effort, and it can run checks and debugging that we hadn’t even thought of. It lets me debug Airflow processes without opening Airflow. It also checks data gaps and table statuses in our databases automatically. I’d say any technical role could get value from it. My company has around 4,000 employees.

Pros: Quick to get started. I was using it right after configuration, and the internal setup guides covered what I needed. It keeps our big MCP hub connected day to day. My quarterly report for a product team used to take me two or three days, and now it takes about half an hour.

Cons: Tools sometimes disconnect until I re-authenticate. It’s quick to fix and I’d call it minor. We also had a recurring broken-connection problem tied to a limit on the Anthropic side, and an update fixed it on our end.

Overall: I’m an AI Supervisor at a company with 1000+ employees. I use Willow to connect Claude to our internal MCPs for CRM and ticketing data, metrics, customer feedback, and help center articles. There’s a Slack team that helps when questions come up. I’d recommend it to any organization with many internal connections. My company thanked me for writing this review.