Willow

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.

Pros: I set it up myself in about 2 days, with no help from IT. I connected Claude to Gmail, Drive and Monday. I’ve never had to reconnect anything. It’s quiet and easy.

Cons: Nothing so far! i really like it and would recommend it to anyone

Overall: I’m a partnership manager. I use Claude through Willow to go through my morning emails, so I don’t have to read all of them myself. I’d suggest it to people with heavy email.

Pros: I’m a data team lead, and I use Willow to connect Claude to Chrome, Slack, Figma, Stash and other connectors. A teammate and I set it up in about half a day, and it mostly runs on its own. It pulls context from images, documents and Drive files I share, which is how I put together a “Measuring Our Products” presentation in 2 hours. Similar ones used to take me several days. I also have an agent that summarizes my team’s Slack channel into weekly action items.

Cons: The one real downside is that I have to re-authenticate every several days, and it’s most annoying when it hits right after I send a prompt.

Overall: I’d recommend it to anyone who isn’t doing strictly manual labor. For me it cut a multi-day deck down to 2 hours, and the only real friction is re-authenticating.

Pros: It gives me a solid first pass in seconds when I draft and summarize internal updates.
I don’t track the minutes, but it noticeably cut down the time I spend writing and editing communications.
It’s connected to our databases and knowledge articles and searches them for the best answers.
I don’t do any admin or upkeep. Someone else manages the connections, permissions, and knowledge base.

Cons: Once in a while I check that the info is current before I use it.

Overall: I work in support at a company of about 5,000 people, and Willow is our internal help system. It took about a week of learning after it was already running to get comfortable with it. It’s good for teams that spend a lot of time drafting routine updates or searching internal documentation.

Pros: I've been using Willow for about six months as a UX designer to connect AI tools through MCP. What I like most is how automatic it is: once it's set up, the connections just work and I don't have to put in any real effort to manage them. That lets me focus on my design work instead of on configuration.

Cons: Honestly, I haven't run into any real problems so far in six months of use.

Overall: Willow has been a great experience. It handles MCP connections automatically, so I get the integrations I need with almost no effort on my side. Disclosure: my company works with Willow.

Pros: I use Willow to connect MCPs to Claude Code. I use it with Slack, Jira, GitHub, Grafana, Trino, Google Workspace and some of our internal tools. Our platform team did the setup and I only had to run one command. It saved me a lot of time because it showed me integrations I could use that I didn't know about.

Cons: I need to log in again sometimes, though that may be our IT policy.

Overall: I'm a developer at a company with about 4,000 to 5,000 people. Good fit for devs using Claude Code with lots of internal tools.

Pros: I'm a developer at Wix and use Willow with Claude Code and Codex to reach Slack, Jira, Figma and Gmail. Setup was fast and simple, I got all the MCPs I needed connected in one go. Before, I had to connect each MCP separately and kept getting logged out. Now it just keeps working with no upkeep.

Cons: Nothing major so far. It's been working without me having to touch it. If you work alone with only a couple of tools it's probably not needed.

Overall: It fixes the auth hassle of using a lot of MCPs at once, so I just use Slack, Jira, Figma and Gmail from Claude Code and Codex and get on with my work. It's a good fit for anyone at a company with a lot of tools. I got a gift card as a thank-you for writing this review.

Pros: Setup is easy. Before, I had to understand the MCP configuration myself. Now I copy the prompt Willow gives me and paste it into the agent. It took me about 2 minutes and I did it on my own. It works with both Claude and Cursor.

Cons: I have to re-authenticate. That’s the only upkeep, and nothing else has bothered me so far.

Overall: I lead a data group at Wix and use Willow to connect our company’s MCPs to my AI tools. It removed the configuration work for me. I’d recommend it to any organization or individual that uses MCPs. I got a thank-you from Willow for writing this review.

Pros: Pulls updates from monday, Slack and our internal knowledge articles, so I update internal articles way faster.
Helps me resolve cases and write training and internal material.
Connects to Slack, Jira, monday and our SRM.
Mostly runs on its own once it’s set up.
Easy to recommend to anyone. It can only help.

Cons: Opens a new tab that I have to close manually

Overall: I work in customer care at a company of 1,000+ people. I use Willow with Slack, Jira, monday and our SRM to answer cases and write training and internal material. The biggest win is internal knowledge articles. Willow pulls the updates on a feature from monday, Slack and our existing articles, so I update the article way faster. Setup took a month or two and I needed IT at first, but now I handle it myself. The one annoying thing is that it opens a new tab I have to close manually. I’d recommend it to everyone. It can only help.

Pros: I'm a UX designer at a company of about 3,500 people and I've been using Willow with Claude for several months. I build features from the product stage through to shipping, and Willow connects Claude to the tools I need: Figma MCP to turn designs into code, Babel for translation keys and our localization process, and Trino and Quix for data questions. The connections run in the background, which makes the work fast and easy. One limitation: now and then a connection drops and I need to reconnect, but Claude flags it and it takes seconds. I'd recommend it to people who work with a lot of MCPs across different tools. I got a gift card as a thank-you for writing this review.

Cons: Not much, honestly. Every so often a connection drops and I need to sign in again. Claude flags it and it takes a few seconds, so it's a small thing.

Overall: I'm a UX designer at a company of about 3,500 people and I've been using Willow with Claude for several months. It's become part of my daily work. I'd recommend it to people who work with a lot of MCPs across different tools. I got a gift card as a thank-you for writing this review.

Pros: I use the Willow MCP portal to connect the MCPs for Slack, Jira, Fire Console, GitHub, Rootly, Grafana and Octocode to Claude. The moment it clicked for me was a bug I had to investigate. I connected Grafana and Fire Console, and those two got me to the cause and the fix in a few hours. By my own estimate that would have taken several days before. That’s when I realized how much these tools can change the way I work. There’s also nothing much to maintain week to week.

Cons: At the beginning I had to re-authenticate often. It’s improved a lot since then.

Overall: I’m an frontend engineer at a company of around 100 people. Willow lets me connect my tools to Claude. Kickoff to first real use took about a week, and I set it up with some help from teammates. I’d recommend it to anyone who already uses Claude and wants their tools connected to it, and to engineering teams who want to work better, faster and easier. I’m getting a thank-you for writing this review.

Pros: Getting started was one command, npx @mcp-s/cli login, and I was up and running. My AI agent (Claude Code) reaches Jira, Slack, Grafana and other internal tools through one gateway, and week to week there's almost nothing to maintain.

Cons: The login token expires from time to time, so I have to log in again in the browser. It's quick, but it's a small annoyance.

Overall: I'm a team lead at a large company and use Willow every day to connect my AI agent to the tools I work with. If your team uses AI agents and wants one gateway to its tools, it's worth a look. I got a thank-you gift card for writing this review.

Pros: It connects Claude to the tools I already work in. I send Jira tickets, edit Figma screens and check prompts from Claude, so I do a lot less by hand. I started using it right away, and the setup doc was all the help I needed.

Cons: Nothing major stands out for me. The only upkeep is re-authenticating when it prompts me, and it always tells me, so it’s easy.

Overall: I’m a UX writer at a company with 1,000+ people, and Willow saves me a lot of time by letting Claude connect to my tools. I’d suggest it to anyone who uses Claude a lot and wants to save time and effort.

Pros: I’m a localization expert at a company of about 5,000 people, and my work is spread across a lot of tools. With Willow I’ve got Smartling, Monday, Jira, Slack and an internal tool all connected. I use it to manage my projects, keep my Monday boards up to date, follow my Jira tickets and create content in our internal tool. Recently I had a huge project with 4 Monday boards to update. They had the same info but not in the same order or with the same logic, so normally I’d have had to look up each of about 100 items in all 4 boards one by one. Since everything was connected, it all got updated automatically and I didn’t even have to open a board. Real time saver.

Cons: I have to reconnect from time to time and I don’t know why. It’s quick and not complicated, but it’s a bit annoying.

Overall: My work lives on several platforms, and keeping them all up to date by hand takes time. Willow connects them, so I can update and follow everything without jumping from one tool to the next. My whole team installed it at the same time and I started using it right away, mostly for tests at first. I’d recommend it to anyone who works across several platforms and needs to centralize and simplify their processes.

I’m getting ₪200 for reviewing Willow on SourceForge.