Willow

Pros: Setup took me minutes, and I did it with Claude.
We run MCP connections to Slack, Jira, GitHub, Monday, Google and internal tools through it, and every AI client we use works with it, and every AI client we use works with it.
Using internal MCPs through Claude feels about 10x faster for my day to day work.
There’s basically nothing to maintain week to week.

Cons: The one thing I’d improve is figuring out which internal MCPs exist and what each one does.

Overall: I’m a software engineer at a large tech company.
Using internal MCPs through Claude feels about 10x faster for my day to day work.
It fits companies that use a lot of AI tools and want their employees to use them.

Pros: I use Willow with Claude Code to hit Jira and Grafana, and that’s what I mostly use it for. Setup was quick.

Cons: It used to ask for auth way more often than I wanted. That’s been getting a lot better though.

Overall: I’m a software dev at a 1,000+ person company. When something breaks I have Claude check the Grafana logs, and before I start coding I have it read the Jira ticket.

Pros: Easy to set up. It took me about 30 minutes, and I was using it for real work the same day. It’s fast and reliable, so I can just get on with troubleshooting and not think about anything else. It’s connected to Git, Slack, CLI and a mix of internal and external tools, so I can check a lot of sources and pull a lot of information, which I couldn’t do without it.

Cons: Nothing big. I do have to re-authenticate, but that’s for security, so I don’t count it as a problem.

Overall: I’m in product support at a company with over 5000 people. I use Willow for debugging conversations, support emails, dev escalations, credit complaints and case history lookups, and it saves me a lot of time. Great tool for teams without deep tech knowledge.

Pros: Effortless onboarding for end users
One identity and one access model across all tools
Connectors keep growing without any work on my side

Cons: Needs VPN
Connector health isn’t visible when something fails

Overall: Willow became part of my daily workflow almost without me noticing. As a production engineer, I let my Claude agent move across Slack, Jira, Google Workspace, Grafana and our internal platforms from one place, with no extra setup for each tool. The best part is the speed of going from question to answer: the agent gathers context from several systems and acts on it in one session. It feels like an enterprise integration layer built for the agent era.

Pros: One Willow connection in Claude Code gives me Jira, Slack, Grafana, GitHub search and our AppSec findings tools in one place.

Cons: Huge tool list, hard to find the right one fast! I recommend though

Overall: I'm in AppSec at a 4K-person company. We use Willow to connect our tools and MCP servers. really improved work.

Pros: i use willow to connect claude and codex to almost every internal system we use at wix. setup was pretty self service, and there's pretty much no ongoing maintenance.

Cons: the annoying part is that agents sometimes forget to use the cli and try getting the data through the browser instead, like with monday or jira.

Overall: i'm a development team lead at Wix, and willow helped me create and debug multiple BI events in Wix's internal BI system, something i'd never done before. i'd recommend it to knowledge workers at organizations using both external and internal systems.

Pros: I use Willow to find and connect MCP servers to Claude Code, as well as plugins. The search is really easy to use, and whenever I need a specific MCP server, I can usually find it in seconds and have it ready to use almost immediately.

The initial setup took me just a couple of minutes, and I did everything myself. After that, everything mostly just works without needing much maintenance.

Cons: Nothing so far. Everything has been working great for me.

Overall: It gives us one central place to find and access MCP servers instead of having to manage everything separately. As a Data Engineer, it's really convenient to quickly find what I need, connect it to Claude Code, and get back to work.

Pros: Willow’s connections let me stay in Cursor or Claude and work more efficiently. We use it for MCP servers like Playwright and Trino, and people across the company use it. It mostly runs without me touching it.

Cons: The one annoying thing is that you sometimes have to re-authenticate.

Overall: I’m an integration manager at a company with 1,000+ employees. My team was involved in getting Willow going. I’d recommend it to anyone who uses AI and MCP a lot.

Pros: I use Willow to connect Claude Code to all our MCPs, internal and external. When I mention Jira, Slack or Figma in a prompt, Claude knows to go through Willow and connect. It pulls the Jira tickets so I don't have to copy anything, and with Figma I just give it a link to the page I need to implement and it handles the rest. Setup was easy too, there was a session about Willow in my onboarding and we configured it right there.

Cons: The Re-auth is a bit annoying. I have to do it fairly often.

Overall: I'm a software engineer at a company of about 4,000 people and I use it on almost every task. If you're using a lot of MCPs with Claude Code, it's worth it.

Pros: I'm a software engineer at a company of about 4,000 people. I use Claude Code inside Superset all day, and Willow is how all my MCP servers reach it. That's 16 of them through one toolkit: Slack, Trino, Grafana, Figma, Monday, Google Workspace, our builds and rollouts, feature toggles, DB tools, incidents, and more. One URL, one login, and it follows me into every new session. Setup took me about 5 minutes, and I did it myself.

The moment that sold me: I rolled out a feature toggle from employees to all users from one Claude chat. Claude read the release, hit the mandatory wait, skipped it step by step with monitoring on, and checked the result. It took about 2 minutes, and I never opened the Releases UI. Another MCP for the same thing timed out that day. The one through Willow worked first try.

Week to week there's almost nothing to maintain. I haven't noticed any re-auth. It just works.

Cons: When I add a new server to my toolkit, I have to reconnect in /mcp before the session sees it. The bigger issue: some tools also come from plugins and claude.ai connectors, so the same tool shows up two or three times. Claude sometimes picks a copy that doesn't work. Big servers also crowd the tool list.

Overall: I'm a software engineer at a ~4,000-person company, and I use Willow to connect Claude Code to everything I touch daily: Slack, Trino, Grafana, Figma, builds, feature toggles, DB tools and more. Setup took me about 5 minutes, and since then it's one login that works in every session with almost no upkeep. Once I rolled a feature toggle out to all users from a single Claude chat in about 2 minutes, while another MCP for the same job timed out that day. My main gripe is duplicates: the same tools also come from plugins and claude.ai connectors, so Claude sometimes picks a copy that doesn't work, and big servers crowd the tool list. Adding a new server also means reconnecting in /mcp. If you work with many internal tools from an agent, it's worth it.

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

Pros: I’m a frontend dev at a 1000+ person company, and I use Willow with Claude Code. It’s connected to our Slack, Jira, GitHub and internal MCPs. I give it a link to a ticket or a Slack thread, or both, and it fixes bugs or helps me push features forward, and I use it to check PRs too. I set it up myself and there’s basically no upkeep. Re-auth has been pretty easy when I needed it. No real downsides for me so far, and I’d point it at teams with a lot of internal tools.

Cons: Sometimes I have to re-auth, but it’s pretty easy.

Overall: Willow is how Claude Code gets to our Jira, Slack, GitHub and internal MCPs. I give it a ticket or a Slack thread and it works on the bug or the feature. Setup was on me and upkeep is basically zero. Good fit for teams with a lot of internal tools

Pros: I lead a dev team at a 1000+ person company, and we use Willow for MCPs and skills: Jira, Slack, Grafana, plus custom ones we built ourselves. The Grafana MCP changed how we check production issues. Before, we'd go into the code and dig through Grafana logs, and now I give Claude the error or a request id and it finds the issue in the logs. What took hours now takes minutes. Once the company's infra was in place, a new custom MCP or skill took us a couple of days to set up. Limitations: nothing major so far.

Cons: Nothing major so far.

Overall: I lead a dev team at a 1000+ person company, and we use Willow for MCPs and skills: Jira, Slack, Grafana, plus custom ones we built ourselves. The Grafana MCP changed how we check production issues. Before, we'd go into the code and dig through Grafana logs, and now I give Claude the error or a request id and it finds the issue in the logs. What took hours now takes minutes. Once the company's infra was in place, a new custom MCP or skill took us a couple of days to set up. Limitations: nothing major so far.

Pros: I’m a product solution engineer and I use Willow for auth on our MCP servers, in both Claude Code and Cursor. Before this I generated a personal access token for every system by hand, and redid it every time one expired. It was a nightmare. Now it’s one login and GitHub, Jira and our internal platform tools are just there for my agents. Our security team spent about a week getting it stood up. For me it was less than a day.

Cons: The session doesn’t hold. I’m re-logging in multiple times a day. It’s a small hassle and honestly it’s the only thing I’d change.

Overall: It takes the per system token work off my plate. I’m not generating tokens or redoing them when they expire, so my agents in Claude Code and Cursor can reach GitHub, Jira and our internal tools without me stopping to fix credentials. My team is around 20 people at a company of about 3000. I’d tell any colleague here to use it. A solo dev with one or two systems probably doesn’t need it.

Pros: It’s been zero touch since, apart from an auth page that shows up now and then. The win I remember: a 4000 word AI written Jira ticket that I linked and had Claude explain to me instead of reading it. Good fit for anyone managing AI tooling for a lot of people who need to keep sketchy downloaded MCPs off company machines. Solo devs can do that triage themselves and skip it.

Cons: agents still tend to pick the direct MCP server over the Willow one when both exist, so discovery could be better.

Overall: I’m a dev at a ~4000 person company and Willow became our required path to Jira, Slack, Google Docs and other MCPs after direct connections got blocked. It’s been zero touch since, apart from an auth page that shows up now and then. The win I remember: a 4000 word AI written Jira ticket that I linked and had Claude explain to me instead of reading it. Good fit for anyone managing AI tooling for a lot of people who need to keep sketchy downloaded MCPs off company machines. Solo devs can do that triage themselves and skip it.

Pros: I use Willow through Claude to check User Voice quotes and tickets for PREX research and decks. I set it up myself and was using it the same day. What I like most is how fast I get to the real quotes and tickets behind an issue. I built a deck for work in a few hours. Without it, that would’ve taken me a few days at least.

Cons: Not much so far, but I’ve only used it for a short time. One small thing: the data is live, so quote counts went up a bit between my checks as new quotes came in. I had to go back and update the numbers in my PREX before submitting. Not a big deal, just recheck your numbers before you share anything.

Overall: Same-day setup, and a deck done in hours

I’m a product expert at a 1,000+ person company, and I use Willow through Claude to check User Voice quotes and tickets for PREX research and decks. I set it up myself and was using it the same day. I built a deck for work in a few hours, which would’ve taken me a few days at least without it. One thing to watch: the data is live, so quote counts went up a bit between checks and I had to update numbers in my PREX before submitting. I’ve only used it for a short time, but I’d recommend it to other product experts doing PREX research.

Pros: I use Willow every day at Wix. It's how my Claude Code agent reaches our internal tools over MCP, for example opening Jira bug tickets straight from my dev session. I don't set up or maintain connectors myself, they're just there. We work with the Willow team a lot and they've been really good to work with.

Cons: Honestly nothing major has bothered me so far in daily use.

Overall: We rely on Willow every day at Wix to connect AI agents to internal systems, and the team behind it is great to work with.

Pros: I'm a dev at a large company and I've used Willow since around June to connect Claude Code to our ticketing, chat, monitoring, design and internal admin tools with one login. I set it up myself, and tool search makes it easy to find the right tool when a lot of servers are connected. Earlier this week Claude used it to check a list of old experiments across a few internal systems in about 15 min, and it caught that the cleanup list was out of date before we turned anything off.

Cons: The MCP tokens expire. Today most of my connections failed with 401 at session start while the CLI was still logged in. I'd want them to refresh on their own, or one login for both.

Overall: It's how I reach internal systems from Claude Code now. Work that touches tickets, logs and experiment settings happens in one session instead of me clicking through each admin tool. Auth is the one thing I'd fix. I got a gift card as a thank-you for writing this review.

Pros: Willow puts all the internal MCPs we have at Wix in one place, plus Grafana, Trino and many more, and Claude uses them from there. Setup was just me and I could use it right away, and there's not much upkeep since Willow keeps the authentication going.

Cons: When I switch my Claude login, the MCP sometimes gets disconnected.

Overall: Looking into logs is a pain. The best time saver for me was a support case where a user had errors, and Claude checked the logs, found the issue and fixed it. I'd recommend it to any organization with a lot of internal tools that wants to expose them as MCPs.

Pros: I’m a data engineer at Wix and I use Willow to hook up Airflow, GitHub, Slack, Jira and our internal tools through the Claude Code extension in VS Code. Setup was easy, minutes on my own computer, no IT involved. What I love is asking one question and watching it activate five different MCP tools in the background, then getting an answer based on a lot of sources. It helps us extract data and analyze it fast. The one thing I’d change is that I have to re-auth every couple of days.

Cons: I Have to re-auth every couple of days , but thats take a few seconds.

Overall: Easy to set up and it does the one thing I need, pulling from all my systems in one question. The re-auth is minor.

Pros: The best part is not copy-pasting anymore. Claude reads a Slack thread and can answer for me, or reads the error logs in Grafana itself.

Cons: The one downside is that I sometimes have to reconnect to an MCP.

Overall: I’m a developer at a company with 1000+ people, and I use Willow to connect MCPs to my Claude. Mine are internal tools, GitHub, Slack, Grafana and a few more, and my team uses it too. Setup took a few minutes, and we got an email from the company explaining how to use it. It helps me all the time. I’d recommend it to anyone using agents, since it makes the job faster.