Willow

Pros: I'm a developer at Wix and use Willow with Claude Code and Codex. I set it up by myself and it was quick.

Cons: The one limitation is that it asks me to reconnect every couple of days, though that only takes a moment.

Overall: Fire Console, Slack and Jira work in both tools without logging in to each MCP separately or doing extra setup. I'd recommend it. I received a gift card as a thank-you for writing this review.

Pros: I run AI operations at a mid-size company, and Willow is our central MCP gateway for Claude. The best part is simple. I set up a connector once and everyone in the company can use it in Claude. I don't have to repeat that setup for each person.

Cons: Connector auth issues. It also isn't set-and-forget. There's regular admin work every week.

Overall: We're rolling Claude out across the company, and we needed one place to manage our connectors. Willow is that place. Getting to real use took over a month. It involved me, our IT/Security team and Willow's team. Now new connectors reach everyone from one setup. I'd recommend it to companies rolling out Claude. For a small team using only a few tools, it's probably more than they need.

Pros: I’m a PM at a company with 1000+ people, and I use Willow to connect my tools to Claude Code. I use Jira to create and query tasks, plus Slack and some of our internal data systems. The big win is getting all of them in one go instead of connecting each one separately.

Cons: Sometimes I have to re-authenticate, but not often.

Overall: I’d recommend it to companies of any size, especially for PMs and other non-technical roles.

I got a gift card for writing this review.

Pros: I connected Ahrefs, GSC and Monday to Claude through Willow, and now I don't pull anything myself. Claude does it. I use it for keyword research, briefs, checking clicks and traffic drops. It works across my two Claude accounts, and I never have to reconnect anything or deal with tokens.

Cons: Setup took about 10 minutes, but I had to ask for help because the instructions weren't clear enough.

Overall: My whole team uses it now. For me there's no upkeep at all, Claude just pulls what I need. I'd recommend it to anyone who struggles with Claude connections.

Pros: Easy to get skills that fit how we work at Wix.
Connects Claude to Google Calendar and Drive.
Helped me write my own skills (daily summary, new-ticket prep) that save me a lot of time.

Cons: Re-authenticating connectors, though it’s not that bad

Overall: I’m a backend engineer at Wix and I use Willow with Claude. I use it to get skills that fit the company and to connect Claude to Google Calendar and Drive. With Claude also connected to GitHub and Google Docs, I wrote skills that summarize my day and prep me for a new ticket, and they save me a lot of time. I set it up during onboarding and was really using it 1-2 months later. My one gripe is re-authenticating connectors, though it’s not that bad. Good fit for people who use a lot of agents day to day.

I got a gift card as a thank-you for writing this review.

Pros: I'm a UX writer, and Babel is where I feel it most. Before, it took me a long time to figure out which project the keys should go in, what to name them, and then to actually add them to Babel. Now Claude does that with Willow in a matter of seconds, even when I need hundreds of keys. That alone has saved me days of work. I also use it to see which keys are live in production on certain screens. Beyond Babel, I use Octocode to research the code and understand how our products behave, GitHub to open PRs for my changes, Jira to create tickets for features, Trino, the data platform and Event Snitch to pick BI events and look at user behavior, and Playwright to test flows and debug errors. All of it goes through Willow. Someone on my team helped me set it up and I was using it pretty much right away.

Cons: Every few days I have to log in to Willow and reauthorize. It breaks my flow, and a lot of the tools I depend on don't work until I do it.

Overall: Overall, it's really great. It makes me more independent. Things I used to need a teammate for, or would get blocked on, I can now do myself. That's why I'd recommend it to whole teams with people in different disciplines. No matter what someone does, it saves a lot of time on everyday tasks.

Pros: One install, Wix sign-in, and Figma, Slack, Jira and GitHub all work in the same chat.

Cons: Connectors sometimes drop mid-session and ask me to log in again.

Overall: I'm a product designer at Wix. I use Willow through Claude Code to reach Figma, Slack, Jira, GitHub and our A/B testing tools from one place. That lets me fix small UI bugs and check experiments myself, without a developer setting things up. The weak spot is connectors that drop and need a new login. I'd recommend it to any company that wants to give non-developers safe access to internal tools. I received a thank-you for writing this review.

Pros: I’m a data engineer and I use Willow in Cursor with the MCPs I need every day: Trino, OpenMetadata, Airflow, and Slack. It turns them on automatically so I don’t have to do that myself almost every day, and after setup it’s mostly hands-off.

Cons: Took a couple weeks to get to first real use with me, my guild, and the data org.

Overall: ’m a data engineer (1k–5k company) and I use Willow in Cursor with Trino, OpenMetadata, Airflow, and Slack. The useful bit for me is it turns the MCPs on automatically instead of me doing that almost every day. Setup to first real use took a couple weeks with my guild and the data org. After that it’s mostly hands-off. I’d point anyone who works with MCPs at it. Honest limitation: I don’t have a strong product complaint, but that couple-week kickoff wasn’t instant.

Pros: Setup was really easy. I did it alone. I use it to work with the company’s MCPs, like Slack, GitHub and Jira. Once it’s connected to those, it has more context, so it analyzes problems better and there are fewer back-and-forths. Upkeep is basically none.

Cons: When an MCP fails, Willow doesn’t try to find out why it isn’t working, and it doesn’t fix it on its own. I’d like it to do that.

Overall: I’m a software engineer on a mobile team at Wix. I ask Willow to Slack my teammates a summary of my work, which helps speed up work on features. Because it can see the tools we already use, I spend less time going back and forth to explain the problem. I’d recommend it to devs who work a lot in a team and need good sync through the week.

Pros: It perfectly collects all of my tasks and projects into a single, easy-to-manage place. This central hub has significantly streamlined my daily workflow and keeps me highly organized.

Cons: The application requires authentication too frequently, which can slightly interrupt my workflow when I am trying to get things done quickly.

Overall: I absolutely love this product because it has truly made my life easier. Having everything organized in one central dashboard is a massive boost to my daily productivity, despite the minor login annoyances.

Pros: I use Willow to connect every MCP I need for my daily work. Connecting, reconnecting and managing them is easy. Each morning I check all my connections in one click, and they’re all under MCPs, so I can see what’s connected and what needs connecting. Setup took one session, and the only thing I needed was IT approval. I do nothing else to maintain it.

Cons: It doesn’t know which tools I usually connect to. I’d like it to learn my usual set and connect to all of them automatically every morning.

Overall: Willow makes it simple to keep all my MCP connections visible and working. I’d say it’s good for big and small companies that want to organize their AI work. I received a thank-you for writing this review.

Pros: I use Willow for all my mcps in Claude Code: github, jira, grafana, trino, gmail and more. Set it up alone in minutes. Adding a new mcp is just one url, no tokens per tool, and if a teammate needs one I just send them the url.

Cons: Only thing is I need to reauthenticate sometimes but its easy.

Overall: I'm a full stack developer at a big 1000+ company. It is good for everyone working with a lot of mcps.

Pros: Setup took minutes and I did it on my own. I connect Claude Code to Jira, Slack, GitHub, Trino and Grafana through it, and it handles the auth and permissions for all of them. When I was reviewing a PR for a bug fix, I could load every tool I needed in one session to check the bug was real and that the fix worked.

Cons: I have to re-auth every few days. It's quick, but it should happen automatically.

Overall: I'm a backend engineer at a company of around 4000 people, and Willow is how I get my MCPs into Claude Code. Upkeep is just re-auth and adding new MCPs now and then. If you're a developer with multiple MCPs and plugins, use it.

Pros: I use Willow at Wix to give Claude Code access to Trino, Quix, Airflow, Slack and Google Workspace without setting up any of those connections myself. Access follows my existing permissions, so there are no separate credentials per tool. It helped most when I switched teams and had to learn a new domain quickly, since I could pull jobs, DAGs and Slack history into one place. It also works from scripts against the same endpoint, which I've used for bulk changes.

Cons: Big responses get cut at 100k characters, and each connector's login expires on its own schedule, so long jobs need care.

Overall: It's become the default way I reach internal data from an AI agent, and it saves me from maintaining my own connectors. I'm getting a BuyMe gift card from my company as a thank-you for writing this review.

Pros: Great for anyone who works heavily with AI, since you become the conductor of the orchestra. it ease my workflow in so many aspects

Cons: needs a lot of reauthentications, but i believe it's not related to willow actually

Overall: I run a bunch of MCPs from Cursor, Claude, and Superset through Willow. It helps me on daily basis to implement my tasks, to debug plenty of bugs using our team's skills that uses MCPs

Pros: Setup was super fast and didn't involve anything special or time consuming. Every time I connect a new MCP it takes seconds. I can connect Trino, Google Docs and Sheets, and some internal Wix MCPs to Claude Code from one place, which is really helpful.

Cons: I have to reauthenticate a few times a week when Claude tells me to. It only takes seconds. It used to happen multiple times a day, but that seems to be fixed since I haven't seen it in a while.

Overall: I'm a data analyst and I've used Willow for about 6 months, in VS Code with Claude Code. I use Google Docs and Sheets daily and I haven't created a single doc myself since I started using it. I'd recommend it to anyone who works with multiple tools and needs a lot of different connections. I received an incentive for writing this review.

Pros: I'm a TL in Wix's server infra group and I use Claude Code, Cursor and Codex day to day. Willow puts the same internal tools behind all of them: Grafana, our DevEx build tooling, Slack, Google Workspace and a few internal MCPs. Someone else set it up, and once it was running, connecting my clients was easy. No upkeep on my end, it just works.

Cons: Nothing comes to mind yet. I've only used it from the client side so far, so I can't say anything about what admin looks like.

Overall: Fewer tabs. I use it to check build failures without opening Buildkite, look at Grafana from Claude Code while on call, and pull Slack threads into Cursor for context. All of that happens inside whichever client I'm already in. I'd recommend it to engineering teams that use more than one AI coding client and want the same internal tools in all of them. If you're a solo dev with one or two MCPs you can configure by hand, you probably don't need it. I got a small gift voucher as a thank-you for writing this review.

Pros: Willow connects to Kiwi, where I write, and to Monday.

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

Overall: 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.

Pros: I'm a developer at a company of about 5,000 people. We use Willow's MCP toolkits to connect Claude Code and Cursor to Slack, Grafana, fire-console, Trino and Figma. Setup took about an hour with a teammate. For one usage question, Claude Code queried Trino, checked Grafana, called a service with fire-console and posted the result to Slack in about 20 minutes. By hand that would've taken me half a day.

Cons: Claude sometimes asks me to re-authenticate the MCP connections, and upkeep is about 20 minutes a week.

Overall: It's a good fit for dev teams on Claude Code, not for non-technical people. I got a thank-you for writing this review.

Pros: It connects our internal MCP servers to Cursor and handles the authentication, so I don’t have to. We also use it for internal apps we rely on every day. Setup took hours, not days. It was just me and my direct manager. After that it mostly runs on its own. My weekly upkeep is adding new MCP servers when we need them and fixing a broken connection now and then.

Cons: Sometimes I have to connect to Willow all over again, even more than once in the same day. It’s a small thing, but it’s annoying when I’m in the middle of a ticket.

Overall: I’m an integration manager at a company with 1,000+ employees. When I work a ticket and let Cursor help, it goes through Willow to authenticate and then runs things in Firebase Console for me. It pulls data, checks a status, and changes a setting. I’d say that saves me roughly 30 minutes on each ticket. I’d recommend Willow to any company that has internal tools and MCP servers. I received a thank-you for writing this review.