Willow

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

Pros: I use Willow to connect Claude to Jira and Figma. Getting it working took a few minutes, and it worked right away. It's now part of how I work every day and it's been reliable.

Cons: Nothing has bothered me so far. I've only used the Jira and Figma integrations, so I can't say much about the rest.

Overall: I'm a product manager on a team of 10. I wanted Claude to work with the tools we already use, mainly Jira and Figma, without a long setup project. Willow gave me that in a few minutes, and I use it every day.

Pros: I lead a backend team at Wix and we use Willow to connect our AI agents to GitHub, Grafana, Jira and Slack. Having all of those behind one gateway means I don’t have to set up and look after each MCP separately.

Cons: Not much to complain about yet; I’d like more visibility into what agents call.

Overall: Good fit for a backend team at a company our size (around 4,000 people) that wants agents working with GitHub, Grafana, Jira and Slack without wiring up each MCP by hand.

Pros: IT set Willow up for me and I was using it within a week. I connect Jira, GitHub, Slack and our internal MCP servers to Claude Code through it, and getting them configured is quick. Upkeep is basically nothing. Sometimes I need to re-auth, but it's really smooth.

Cons: My one complaint is that the UI can be quite confusing at the start, and it took me a while to get a basic understanding of where everything is.

Overall: It's a good fit for big companies that want to organize MCP servers for their employees, but not for solo devs.

Pros: We use Willow as our MCP gateway, and it's how my AI agents reach the tools I work with daily. I don't have to manage MCP servers or tokens myself anymore. Adding a connector is quick, and I use a lot of them.

Cons: The catalog is big enough that finding the right connector can take a minute, and clearer per-connector docs would help.

Overall: Overall it's become part of how I work every day. Instead of every developer wiring up their own integrations, there's one managed way to give agents the context they need. I received a gift card as a thank-you for writing this review.

Pros: I connect once and get the tools my team uses, with auth handled for me. No more setting up and maintaining each MCP server on my own machine, and new tools just show up without me touching anything.

Cons: Nothing big. With a lot of tools available it took me a bit of poking around at first to figure out which ones I actually need.

Overall: I use Willow every day to connect my AI agents to the tools I work with. It's become part of how I work and it stays out of my way. I got a gift card from Willow as a thank-you for writing this review.

Pros: Setup was a copy paste into Codex, and I started using each new MCP right after the announcement went out.

Cons: One downside: early on I had to re-authenticate a few times a day, though that's better now

Overall: I'm a data engineer at a company of about 4,000 people, and we use Willow to connect all our MCPs: Trino, Airflow, Slack, Databricks, OpenMetadata and our DWH MCP. When we built new DWH tables for Base44, I used the Airflow MCP to build and monitor the DAGs, the Trino MCP for the tables and SQL, and the DWH MCP to make sure we met Wix standards. It was all one conversation with every tool I needed, so it was faster and easier. I'd recommend it to any company that wants one place to organize and distribute its AI tools. I received a gift for writing this review.

Pros: Jira, Slack, Sentry, Grafana and Figma all reach Claude Code through the same gateway URL. The only thing that changes is the ?mcp= at the end, so adding a tool is one line in my config and nothing runs locally. Best part is Claude using several of them in one task: read a ticket, pull the Sentry issue behind it, check the Grafana graph, post an update in Slack.

Cons: Now and then a connector asks me to log in again (Figma right now), and tool names come out doubled, like jira__jira__get-issues. Small stuff, it never stopped me.

Overall: Willow is how my Claude Code reaches the rest of our work tools. It's one gateway the company runs, so I just use what's there and the access side is handled for me. I stay in the editor and the context comes to me.