Willow

Pros: Pulls Slack and Jira into one consolidated project update (status, blockers, decisions, action items, owners, deadlines, priorities, open tasks)
Less manual searching and back-and-forth when prepping a project status review
Setup took about 1 to 2 weeks from kickoff to first real use
Mostly hands-off week to week, with nobody managing it full-time
Good fit for product, engineering, and project management teams that live in Slack and Jira and juggle several projects

Cons: Answer completeness can vary. Willow occasionally misses context from a Slack discussion or provides an incomplete picture when Jira has not been updated, so key details still require verification.
Clearer source context and direct links back to the original conversations and tickets would improve traceability.

Overall: Willow pulls project updates from Slack and Jira into one consolidated view: status, blockers, decisions, owners, deadlines, and open tasks. It made prepping for a project status review easier, with less manual searching and back-and-forth. Setup took about 1 to 2 weeks, and it’s mostly hands-off week to week. Answers can occasionally miss Slack context or give an incomplete picture when Jira isn’t updated, so we still verify key details. Clearer links back to the original conversations and tickets would improve traceability. Best for product, engineering, and project management teams that rely heavily on Slack and Jira. Not a fit for very small teams with simple workflows, or teams that need guaranteed-accurate answers without human verification.

Pros: It connects directly to Slack and Jira and saves us lots of time investigating customer issues. We can easily link customer conversations to existing Jira tickets and spot recurring patterns without digging through platforms manually. Week-to-week maintenance is very minimal and straightforward.

Cons: The analysis can sometimes lack flexibility or miss specific context, so we still have to manually verify some insights. Having more customization and clearer filtering options would make it even better.

Overall: I work in customer care at a company with over 1,000 employees. Willow was set up smoothly in a few weeks with our tech team. It helps our team identify trends, understand root causes, and share insights across teams quickly. It is an excellent fit for larger support and operations teams with high ticket volumes.

Pros: When a new need comes up, I go to Willow to check if the tool is approved and available at our company. My department put together a toolkit with all the MCPs that are relevant to me, so I just downloaded that instead of installing each one separately. I also like browsing the skills and plugins other people uploaded. Sometimes I find something I can use, sometimes it just gives me ideas.

Cons: Not much. I'd like to see everything I'm connected to, plus the history, in one place. It's not critical for me though.

Overall: I'm a business analyst at a company of around 4,000 people, and I work with Slack, Monday, Google Workspace and some internal tools. Willow gives me one place to find the tools the company allows and get them. I wasn't part of the rollout, it became available pretty fast and it was clear how to use it. There's no upkeep on my side. I think any company would get value from something like this, since it puts order into how people download these tools, both for control and for security.

Pros: I use Willow with Claude Code to connect to our company MCP and our data warehouse. I just ask Claude questions about my product and Willow runs them. Setup took a few minutes following our IT instructions. Easy.

Cons: I have to reauthenticate every few days when I’m not using Claude. That’s the only thing that bugs me.

Overall: It helped me understand my product better and plan what’s next, and I didn’t have to depend on our BA analyst for it. Probably saved me a few hours for every task. It just makes it easier for everyone.

Pros: I connect Jira, Figma and Slack to my Claude through Willow. I pull Jira tickets in and Claude writes the specs. That used to take me about half an hour each, and now it’s around 2 minutes. It also helps me keep my Figma files organized.

Cons: A few times a week it asks me to reconnect something I thought was already connected. That and managing permissions is most of the upkeep I deal with.

Overall: I’m a UX designer at a company with 3,000+ people. Setup took about half an hour and I did most of it myself, with some help from my manager. I’d recommend it to anyone working with AI, it opens up a lot of capabilities. I wouldn’t recommend it to non-tech people who don’t understand these tools yet. I received a thank-you for writing this review.

Pros: I'm a full stack developer at Wix and use Willow every day to connect claude code to slack, jira, google workspace, grafana and trino. It's one gateway instead of a pile of separate mcp setups. It helps me most with production issues:
I pull grafana logs and metrics right into my claude session and work through the problem without switching tools.

Cons: I have to log in again more often than I'd like, sometimes in the middle of a session, which breaks my flow.

Overall: Willow gives us one central, managed way to connect AI agents to company systems. I don't have to handle separate credentials and configs for each tool, and it saves me real time when something breaks in production. It's become part of how I work every day.

Pros: I lead a data team at a 1000+ company and we use Willow to manage our MCPs and plugins: Trino, Tableau, Google Workspace, Slack and monday. I set it up alone in an hour or two, and it was easy. When someone needs access, like to Trino, I don't have to set up the MCP on their machine anymore.

Cons: One limitation is that you can't share a direct link to log in to a specific MCP.

Overall: It fits teams where a lot of people need several MCPs, and it's probably overkill for one person on a single MCP. I received a BuyMe gift card as a thank-you for this review.

Pros: I'm a principal data engineer at a company of thousands. Willow is the layer in front of the tools I call. For me that's Spark, Trino, OpenMetadata, data-to-prod, the profile service, Grafana, Jira, and Babel. I query, look up tables and metadata, check logs and dashboards, and open Jira from there.

Cons: I don't have a specific complaint I've hit and can describe.

Overall: I use it to reach those systems from the agent. The benefit I can point at is the work itself: queries, table and metadata lookups, logs, dashboards, and Jira.

Pros: I use Willow with UserVoice for analytics. I ask questions about our feedback, and it pulls the data and analyzes it accurately. Setup took one day, and it’s been hands off since then.

Cons: There are a lot of options, and it was hard for me to pick the exact skill for my use case

Overall: I use Willow with UserVoice for analytics. It pulls the data and analyzes the questions I ask, and the results have been accurate. I’d recommend it to anyone who needs accurate data analysis and help condensing a lot of information into guiding principles.

Pros: I'm a software engineer on a production team, company of around 4,000 people. I use Willow to connect Claude to our MCPs, mostly Grafana, plus Jira, Slack and our feature release tool. When there's an alert or a war room, I use the Grafana MCP and Claude investigates for me. There's so much data that finding the root cause is hard sometimes. It helps me understand the issue, find where in the code it is and how to fix it. Much faster, especially for complex problems. Setup on my side was fast. The gateway was already there, I just added the MCPs.

Cons: Every so often I get disconnected and Claude asks me to reconnect. Takes a few seconds, no big deal.

Overall: It lets Claude work directly with the systems I use instead of me clicking through each one. Learning a UI and finding things manually takes a lot of time, and this saves most of that. I'd recommend it to software developers or any professional who works with external systems that have an API. Got a gift card for writing this.

Pros: Setup took only a few minutes on my own.

Everything goes through Willow now (analyses, pipelines, queries), so I don't need to use any other MCP.

My agent found tools inside Willow that I didn't even know existed and used them to solve my problem.

Zero weekly upkeep on my end.

Good fit for any organization juggling multiple MCPs.

Cons: Having to re-authenticate too often

Unnecessary for individual devs or hobbyists.

Overall: I'm a business analyst at a 4,000-person company, and everything I run goes through Willow now. Setup took only a few minutes on my own, and all my analyses, pipelines, and queries start with verifying the connection. The biggest win was when my agent located tools inside Willow that I didn't even know existed and used them to solve my problem, with zero weekly upkeep on my end. The main annoyance is having to re-authenticate too often. I'd suggest it to any organization juggling multiple MCPs, but it's likely unnecessary for individual devs or hobbyists.

Pros: It's one gateway for all my MCPs. I use Grafana, Trino, Slack, GitHub, Figma, Mongo, Playwright, EngFlow, DB core, Google Workspace and more from both Claude Code and Cursor. I don't have to configure any of them by hand. I set it up myself in about an hour, and I think it'd be faster now. After that it just works.

Cons: Sometimes I have to re-auth, and it comes up a bit more often than I'd like. Not a big deal though, Claude sends me to the login page by itself when it's needed. Other than that there's no upkeep.

Overall: Without it I'd be setting up each MCP by hand in Claude Code and Cursor. Now it's one gateway and I'm done. It comes in handy in every investigation and design I work on. If you're a dev using a lot of MCPs it's worth it.
I got a gift as a thank-you for writing this review.

Pros: I'm a data engineer at a large company. I built a data MCP on Willow for querying data in natural language. Once I shipped it, people started using it without me walking them through setup. That's the part I like most. Connecting is one click, and all the MCPs are in one place, so people across the company can find the tools and skills that are out there. I also use it for Trino, Slack and GitHub, and I set those up without needing anyone from Willow. Upkeep is almost nothing. It's plug and use.

Cons: The docs are very helpful, but connecting user authentication to the MCP I created was challenging. It took some back and forth with the docs and someone from Willow before I understood the request process.

Overall: Willow lets me connect to MCPs and create new ones with security built in. For our data MCPs that means SSO login and per-user permissions. Getting started was quick once it was available inside the company. It was me and my team, plus someone from Willow for the auth on our new MCP. It makes the most sense for large companies, or anyone with a lot of MCPs, skills and plugins to keep organized. I wouldn't recommend it to small companies with only a few MCPs and tools.

Pros: Very low friction. One toolkit gives my AI agents all the tools I need, and adding a new one takes a minute. The tool kits are great.

Cons: The login session expires now and then, so I have to sign in again.

Overall: Setup was quick and it just works. One toolkit connects my agents to what they need, with my own access. I got a gift card as a thank-you for this review.

Pros: Getting started took minutes. I use it to get to Slack, Google Workspace, Grafana, Jira and several of our internal tools from one place. Jira was the connection that got simpler for me.

Cons: Nothing so far. I'm not involved in admin or config, so I can't speak to that side.

Overall: I'm a QA automation team lead at a company of about 4,000, and it's been easy to use day to day without me touching any setup. I'd point large organizations that need better access controls at it.

I got a gift card for writing this review.

Pros: I’m a PMM on Symphony at Wix, and I mostly use Willow to manage the connectors Claude uses. I set it up alone in a few minutes. It let me connect Claude to Symphony analytics, so now I can pull any product data from Claude directly. I let it run, so there’s no weekly upkeep. I’d recommend it to my coworkers.

Cons: haven’t hit anything annoying or missing so far, and I let it run without any upkeep.

Overall: Willow made it easy to connect Claude to Symphony analytics. I set it up alone in a few minutes, and now I can pull any product data from Claude directly. I’d recommend it to my coworkers.

Pros: I set Willow up myself in under an hour, no help needed. I’ve got it connected to Figma, Slack, Jira and Drive. I use it to open Jira tickets, create Figma files, make spreadsheets, and summarize and send Slack messages.

Cons: Sometimes I need to reconnect. That’s the main thing I’d want fixed.

Overall: I’m a graphic designer at a 1000+ company. Opening Jira tickets manually or creating Figma files used to take me hours. Now it’s minutes. Good fit for anyone working heavily with Claude and other tools who wants to increase velocity. I got a gift card for writing this review.

Pros: Centralizes authentication and token management, so individual engineers never have to handle or store internal production credentials in their local client configs.

Cons: Finding the right tools is hard: with many MCPs and toolkits, there's no guided way to work out which ones your task needs.
Maybe adding some AI "MCP Advisor"

Overall: As a Wix software engineer in wix, Willow has become standard infrastructure for our internal developer tooling. I’d recommend it to any engineering org standardizing their LLM-to-tool workflows.

Pros: Before Willow we connected every MCP by hand and had to auth each one every time. Now new MCPs get registered in their platform and there’s a single auth. Adding a new MCP takes minutes.

Cons: The one thing that still bugs me is re-authing once a day when the token expires. At the start it was every time my computer disconnected, and they’ve improved that.

Overall: I’m a data engineer at a large company and we use Willow to manage our tens of MCPs and skills for Claude Code, Cursor and Codex. Setup took me a day on my own. If you’re a big company that wants control over your MCPs and how they connect to your coding agents, it’s a good fit. I received a thank-you from Willow for writing this review.

Pros: I use Willow to connect Claude Code to our internal tools, mainly Slack, Jira, Grafana, Fire Console, Playwright and Trino. Infra set it up, so getting started was quick, I just connected the tools I needed. Best example: one DLQ alert turned into finding a much bigger gap once Claude Code could pull from Grafana, Trino and Slack together.

Cons: Sometimes I have to click reconnect or log in again.

Overall: I'm a full stack engineer at Wix. Without Willow I think we'd have just fixed the DLQ issue and moved on, without understanding the gap or what it meant. I'd recommend it to dev teams that use Claude Code and need it to reach a lot of internal tools like Slack, Jira, Grafana and data.

Disclosure: Wix is an investor in Willow. I'm getting a gift card as a thank-you for writing this review.