Willow

Pros: one endpoint for all the tools, thats great! github, jira, slack and grafana all work in claude code through the same connection, no separate setup for each one.

Cons: none! really satisfied with the product, it does exactly what i need it to do.

Overall: I’m a software engineer at Wix and I use Willow to connect Claude Code to GitHub, Jira, Slack, Grafana, Google Workspace and our internal tools. It’s all one endpoint, so I don’t have to set up every MCP server separately. I made a personal toolkit with just the tools I need. If you connect a lot of servers, the full tool list gets huge, so you’ll want to narrow it down early. I got a BuyMe gift card as a thank-you for writing this review.

Pros: I’m a data engineer, and I use Willow every day to connect to our internal MCPs, skills and plugins. It’s easy to add new MCPs, and internal ones are available based on my permission group. I built an A/B test MCP with the premium team, and it now powers an automation that runs twice a week and reaches its consumers without me touching it. It’s a great fit for large companies that want to make internal tools accessible to everyone.

Cons: I haven’t hit a real limitation, but I mostly use it for internal MCPs, so I can’t speak to much beyond that.

Overall: My overall experience has been nothing but smooth. I use it on a daily basis and it decreased friction significantly and made me more independent.

Pros: Willow is the one login in front of the tools my Cursor agent calls. The same session reaches Fire Console, root cause, Trino, Spark, Grafana, and Dataverse, and the browser tools from the old Webrix setup. When a call needs a yes, I approve or decline it there. On a DevRel case that is the part I actually want. The agent gets to the internal tools, and I stay in the loop.

Cons: The session does expire. The tools fail, and the error often says Fire Console even though the whole login is dead. I sign in through Okta and rerun the calls. It takes a minute.

Overall: I work in Developer Relations at Wix, and I use Willow as a user on the cases I work. It is how my Cursor agent reaches our internal tools with one login, and I approve a call when it asks. I would point another person on the team who lives in Cursor at it. I was offered a thank-you voucher for writing this review.

Pros: Setup was quick. I added the URL in Claude Code, logged in, and it worked within minutes, nobody else had to get involved. Through it my agent gets Jira and some of our internal tools. The part I use most is debugging: I give Claude a site ID and it calls our internal APIs to read the site's data, so I don't have to click through internal consoles myself. Upkeep is close to nothing. Sometimes the connection drops, I press reconnect and it's fine.

Cons: On Claude Desktop, when I'm on the VPN to reach our internal tools, it opens a lot of Chrome tabs to authenticate and I have to approve them one by one. That's the only real thing that bugs me.

Overall: It gives my coding agent Jira and our internal tools from one place, without me wiring up each server myself. I'd recommend it to teams with internal tools they want agents to use. If you only need one public MCP, you probably don't need it. I got a thank-you gift for writing this review.

Pros: I like ability to work out of the box, share toolkits, forget about mcp and skills profiles switching, share easily with the team

Cons: Only UX and UI not the best, but u mostly use it in cli so does not really matter

Overall: At first, it was not really convenient, because things and ways we work are changing quickly, then we find ways to use tooling and willow predict your need before u realize it.

Pros: We use Willow for authentication on MCP-S, so it controls access to all of our MCPs. Before it I had to do everything manually and it was a nightmare. Now it's one login.

Cons: I have to re-authenticate once a day. It's a small hassle, and it's the only upkeep I deal with.

Overall: I'm a software developer at a company of about 4,000 people. Our security team set Willow up and it took a couple of weeks. Now it's one login for all our MCPs instead of doing auth manually for each one. I'd recommend it to anyone.

I got a thank-you for writing this review.

Pros: This review was provided in exchange for a gift card. I'm an automation engineer at a company with 1000+ people, and I use Willow to authenticate and get access to MCPs. That covers Jira, Slack, GitHub and our internal MCPs, from Claude Code, Cursor and our own agents. Before Willow I stuck to public MCPs, and getting the internal ones working meant a longer manual setup. Now I sometimes add a new MCP that uses Willow, and other than that I have no upkeep.

Cons: Every new MCP needs its own authentication. I'd rather log in once and have it carry over to future ones.

Overall: It improves our company's security, which is why I'd recommend it to any company that uses AI and MCPs.

Pros: My team got it going in about a week or two. It saved me a lot of time on wiring up Grafana, handling auth and credentials, and codebase research. Upkeep is almost nothing.

Cons: re-authentication comes up more often than I'd like, and the few tool failures I hit were hard to troubleshoot.

Overall: I'm a production engineer (SRE) at a company of about 4,000 people, and I use Willow with Grafana, Jira, Slack, Octocode and internal tools for alert triage, incident triage and root cause analysis. My team got it going in about a week or two. It saved me a lot of time on wiring up Grafana, handling auth and credentials, and codebase research. Upkeep is almost nothing. The downside is that re-authentication comes up more often than I'd like, and the few tool failures I hit were hard to troubleshoot. I'd recommend it to anyone working on agentic flows.

Pros: A quick setup and access to all our internal MCP and external ones. Not complicated and worked really fast.

Cons: The one downside is I have to re-auth sometimes, but it's quick.

Overall: I am a software engineer at Wix, and now my agents just have access to the tools I need. I would recommend it to anyone who uses mcp connections on a daily basis.

Pros: I'm a backend developer at a big company and I think I've used Willow for about 6 months.
It helps me find MCPs and skills, shows how to connect them, and handles authorization. My whole team uses it. I'd recommend it to developers in big companies who work with MCPs and skills and want to share them safely.

I received a thank-you for writing this review.

Cons: I haven't hit a limitation yet, so I can't name one honestly.

Overall: Easy to use, good UI, and works great. Helps me find MCPs and skills, connect them, and handle authorization.

Pros: A big CMS update that used to take me days, sometimes a week, took half an hour. Connecting Claude to the Wix MCP for building pages is simple and fast. My manager set it up and I was using it for real work in about a day. Upkeep is almost nothing.

Cons: I’d like an easier way to manage the MCPs I currently have connected. It’s also too technical for regular users.

Overall: I’m a DEV at a company of about 3,500 people, and I use Willow to connect Claude to the MCP for building pages. It’s made CMS updates much faster for me, and I spend almost no time keeping it running. I’d recommend it to colleagues in my field, but it’s too technical for regular users.

Pros: I use Willow from Claude and Codex to connect to Jira, Grafana, Slack and a lot of internal Wix tools. Setup wasn't hard. For alert investigation, Claude reads the alert in Slack, pulls logs and metrics from Grafana, and finds the cause without me switching tools. Sometimes you don't realize you need more MCPs, and on Willow they're all there.

Cons: The one downside is that it logs me out sometimes, though logging back in is easy.

Overall: I'm a software developer at Wix and I use AI agents for a lot of my work. Willow gives those agents access to all the systems I use, so Claude can do almost everything for me now. I'd recommend it to any developer or anyone who works with agents.

I got a BuyMe gift card for writing this review.

Pros: Setup was very quick. I connected the Willow MCP through the terminal, then managed the individual MCPs through the UI.

I can manage MCPs for SQL querying, KB research and asset creation in one place.

I can ask my AI assistant a data question without pointing it to specific resources. It can check our documentation, find the relevant data, then use our querying tool to get the numbers.

Cons: I occasionally need to reauthenticate. That’s been the only upkeep for me week to week.

Overall: I use Willow to manage MCPs for SQL querying, KB research and asset creation. I can ask my AI assistant a data question without pointing it to specific resources. It uses Willow to access our data documentation tools, find the relevant data, then connect to our querying tool and retrieve the numbers. Setup was very quick: I connected the Willow MCP through the terminal, then managed the individual MCPs through the UI. I occasionally need to reauthenticate, but that’s been the only upkeep week to week.

Pros: Willow gives us one central place to manage how our AI tools connect to internal systems through MCP. Before, each team set up its own connections, which made it hard to see who had access to what. Now the connections, permissions, and usage are visible and controlled in one place. For me, that means less time on setup and access requests, and more confidence that AI tools use company data securely. It also makes it easier to adopt new AI tools quickly without having to work out security and access from scratch each time.

Cons: could add a bit more companies to the ui,
sometimes the willow mcp ets kicked out in auth but its easy to reconnect

Overall: Willow made managing our AI tool connections much simpler. Having MCP access, permissions, and visibility in one place saves time and gives us confidence that AI tools use company data securely.

Pros: It puts our MCP services in one place (Jira, some internal services, our company skills) and makes them easy to find. When I needed to verify a feature on a real service, I found a plugin for an internal user-admin tool, added it in Claude, and it logged in as a few test users for me.

Cons: Not much. I have to log in again from time to time, that's about it.

Overall: I'm a developer at a 1k+ company and I use Willow from Claude Code. Our platform team set it up, so on my end it just works. Good fit for anyone who wants their skills and plugins shared and in one place.

Pros: I'm a data engineer at Wix and use Willow from inside Claude Code to reach Trino, Airflow logs, Jira, Slack and GitHub through one CLI. When a prod task fails I ask "why did this task fail last night," and Claude pulls the log, queries the table to check the impact, and then I fix it. Last month that's how I found why a daily email digest DAG kept failing, without opening the Airflow UI or a SQL client once. Setup on my side was installing the CLI and logging in once, and upkeep is close to nothing.

Cons: The write tools that touch prod Airflow sit right next to the read ones, and I'd like read-only by default per user instead of relying on our own rule.

Overall: One authenticated way into our internal tools from where I already work, so I don't jump between the Airflow UI, a SQL client, Jira and Slack to chase down an issue. Good fit for bigger engineering or data teams using AI coding agents. I got a ₪200 BuyMe gift card from Willow for reviewing it.

Pros: All the systems are already connected, so I don't need to think a lot about it. I run my agents in dev3.0 and Willow connects the MCPs. Slack, monday and GitHub are the ones I use most. An agent can take a monday issue, submit a PR and post the update in Slack, start to finish.

Cons: It used to open a lot of browser pages, but the Willow team fixed that. Now I just need to log in from time to time.

Overall: I'm an xEngineer at Wix, about 4,000 people. Willow came as an integration the whole company already works with, so I didn't set anything up. It saves me a lot of time. I'd recommend it to any tech company that works with agents and needs its tools connected.

Pros: I use it as a software engineer to connect my MCP to the coding agents. My company set it up, so I just started using it. I can see all the available tools and how to integrate them in one place.

Cons: Authentication didn't work several times when I tried to use it.

Overall: I'm a software engineer at a company of about 5,000 people. Willow gives me control over my MCPs and the coding agents that use them. I do no admin or upkeep, the company handles that. I'd recommend it to anyone who wants to control their MCPs.

Pros: It connects Claude Code to all the MCPs I need. I use it with Jira, GitHub, docs, Slack, OpenMetadata and Google Drive. Claude can reach all of them, so it writes accurate, good queries on my data. I also don't spend a lot of time explaining context anymore. My organization had it ready to use, so getting started was very fast. I learned it in a guild training session.

Cons: Sometimes I have to reconnect tools. That's minor, and nothing else bothers me.

Overall: I'm a business analyst, and I need Claude to work with my tools and my data. Willow gives it that connection. I save a lot of time on context explanations, and the queries come out good. Besides the occasional reconnect, there's basically no upkeep. I'd recommend it to any organization with organized data, descriptions and presentations. It makes the job easier.

Pros: fast, easy to use
Connects MCP to Jira, Slack, GitHub and Fire Console.
Setup took one day, and I did it by myself.
No regular admin or upkeep.
I’ve used it to find tickets in Jira and post them to Slack.
I’d recommend it to everyone.

Cons: i don't have

Overall: I’m a project manager at a company of about 5,000 people. I use Willow to connect MCP to Jira, Slack, GitHub and Fire Console. I set it up by myself in one day, and there’s no regular upkeep. I’ve asked it to find tickets in Jira and post them to Slack. The one limit I can give is that I’ve only used it with those four systems, so I can’t speak to anything else. I’d recommend it to everyone.