Willow

Pros: I use it inside Cursor, and it lets me check Aria logs, Fire Console, GitHub and Slack in the same sitting. Setup took about a day with my team. Upkeep is almost nothing. It stays signed in on my Wix account, and the only thing I do is an occasional Okta sign-in when Slack or Jira asks again.

Cons: There was no Google Sheets connection. After the Google Tasks and Slides QA, I asked Willow to write the results into our tracker sheet. It could read the Aria logs, the connection and the code, but it couldn't write to the sheet, so I pasted the rows in by hand.

Overall: I'm a technical project manager at a 1,000+ person company, and I run internal projects like the connector work and Aria. While scope-testing the Google Tasks connector, Aria said it couldn't see the connected account. Willow read the logs, the live connection and the code, and showed the grant was already stored and Aria's tools were dropping the account label. I'd recommend it to someone doing connector QA in Cursor who has to check Aria logs, Fire Console, GitHub and Slack at once. I wouldn't recommend it to someone whose work is updating a QA tracker sheet. I received a gift card for writing this review.

Pros: Onboarding was super quick since our platform team already wired up the gateway, so I just ran one setup command, logged in with company SSO, and had all our internal tools working in Cursor within minutes. I also really like the approval prompts on write operations, which keep the agent from posting to Slack or updating Jira tickets before I review the draft.

Cons: Honestly there is not much to complain about so far. Once you get used to having all your internal tools connected in one place, you quickly want every single internal system added to the gateway, and occasionally you still need to approve a quick SSO refresh in the browser.

Overall: I use Willow daily in Developer Relations to connect Cursor to our internal engineering and support stack, including Jira, Slack, Grafana, Trino, and our internal RPC services. It saves me a ton of time during support triage because my agent can pull logs, check site metadata, and search past Jira tickets in one place instead of me digging through five different dashboards.

Pros: I use it to connect Claude to Jira and Slack. Mostly I edit and update Jira tickets right from Claude. I set it up myself with Claude’s help and it was fast.

Cons: Honestly nothing so far. Everything has been working well for me.

Overall: I’m a software engineer at Wix. One time I couldn’t understand a Jira ticket, and Claude read it through Willow and simplified it for me. I think it’s good for anyone who uses AI, it makes life easier.

Pros: It connects Claude and Codex to Trino, our BI catalog, Slack, Jira, Google Workspace, internal docs and logs. I ask data questions in Claude every day now instead of the internal tool I used before. It didn't need IT to get going, and support fixed the one issue I had quickly.

Cons: Re-auth used to be daily and now it's rare. The only thing: the Connect MCP button in Claude didn't reconnect, so I had to copy the command from Willow.

Overall: I'm Head of Product at a company with 1,000 to 5,000 people, and I've used Willow for 6 to 12 months, maybe more. It's basically my gate to all the AI stuff in the company.

Pros: Ease of use. I just signed in and it worked. I use it for all my MCP connections in Claude Code and ChatGPT, including our internal system MCPs, and to find new plugins. When a new MCP was introduced, I connected to it with the Willow CLI very quickly. Re-auth is super simple, a browser window opens and it re-auths automatically.

Cons: Nothing major so far. I haven't hit anything that got in my way yet.

Overall: I'm a developer and tech lead at a 1000+ person company. MCPs and plugins are basically part of working with AI now, and Willow keeps that simple. Re-auth is the main upkeep and it takes no effort.

Pros: I’m a data engineer at a company with about 5,000 people, and I use Willow to manage the MCPs I work with in Cursor and VS Code. That covers our internal MCP plus Slack, Jira, Trino and a few others. The part that actually changed my week is onboarding. Adding a new MCP used to mean opening a support ticket, and rolling something out across the whole company was a complicated process. Now it’s simple and I do it myself. Installs and updates, credentials and access, and seeing what the MCPs are doing all sit in one place. Upkeep is light. Every now and then I re-verify something, and that’s about it.

Cons: The error messages could say more. When something doesn’t connect, I’d like more detail about what went wrong instead of having to go digging. Other than that the system is simple to work with.

Overall: I manage a lot of MCPs across Cursor and VS Code, and Willow keeps all of it in one place instead of spread around. Installs, access and visibility are handled, and onboarding a new MCP no longer goes through a ticket. Upkeep is light, just occasional re-verification. Worth it if you’re a large org with many engineers and many MCPs to manage.

Pros: I use Willow for all the MCPs at my workplace. It just works, and I love it. The MCP-S-CLI is just wonderful.

Cons: I wish reauthentication was less frequent, though that's an organization decision.

Overall: I use Willow for all the MCPs at my workplace, and I love it. MCP-S-CLI is wonderful. I was offered a voucher for an approved five-star review.

Pros: It’s convenient and easy to use. I use it to find MCPs and connect them to Claude and other LLMs. The ones I’ve connected are Jira, Grafana, Slack and Trino. Finding the right MCP is quick, and so is connecting it. I set it up myself, so it didn’t take a team.

Cons: I really don't have anything that i dislike or wouldn't recommend because of.

Overall: I work as a software engineer at a company with 1,000+ people. Willow solves the problem of finding the correct MCP and getting it connected to the LLMs I use. Upkeep is small, since I just add new MCPs as I go. I’d recommend it to companies so their employees can work with it and increase velocity and quality.

Pros: I use Willow to access logs and investigate production issues. It reaches Grafana, the database and GitHub for me. Setup took a few minutes. I never touch configs or permissions, and if I want another MCP I hop over to a dashboard and enable it. It was also easy to use with Google Workspace.

Cons: Nothing really. I have to re-authenticate every few days, but it takes a few seconds, so it's no big deal.

Overall: I'm a software engineer at a company with 1000+ people. Getting started was quick and there's almost no upkeep. I'd recommend it to production minded teams, engineering teams, and people who work in Google Workspace. I received a thank-you for writing this review.

Pros: I’d recommend it to teams that need to sync tools across teams. this very easy to add some mcp's and more AI staff tp the platform

Cons: The one limitation is the CLI config, which was hard to set up and had to be changed each time.

Overall: I’m a data engineer, and I use Willow to connect all our IDEs to Trino, OpenMetadata, Airflow and a lot of custom and external tools. First real use took a few minutes. I had it research across Git repos, find things in Slack, write Trino queries and add the results to a report.

Pros: Willow makes my work with MCPs and AI easier. I use it with Slack, Grafana and BI. Someone else handled setup, so I could start using it right away.

Cons: none that i can think of, it was all was good for me

Overall: I use it for BI investigations and bug fixes. It makes that work easier with MCPs and AI.
Highly recommended

Pros: I use Willow to run MCPs from Codex and Claude Code. Mostly Jira, GitHub and Grafana, and I also have Slack connected. I scan Jira tickets or open them, check GitHub links and ask for code reviews. When I want to understand a Grafana issue I use it for that too. I set it all up myself and it was pretty easy.

Cons: I cant think about any, it is a great product in my opinion

Overall: I’m a software engineer at Wix. I use it every day when I need to understand Jira tasks or GitHub links, and when I’m looking into Grafana issues. Since setup I’ve never had to touch it. It just works. I’d recommend it to anyone.

Pros: 1. Slack, Jira, and GitHub in one workflow instead of constant tab switching
2. Devex repo search, grid code search, and profile lookup when I need the rest of the picture
3. My team started using it as soon as we had access; it fit our day-to-day quickly
4. Light upkeep for me: use what’s connected, add tools when I need them
5. Strong fit for solution engineers and DevRel-style roles at a large company

Cons: Still room to use more of what Willow can connect, I’m not maxed out yet.

Overall: I’m a solution engineer at a 1000+ company. Willow hooks into the systems I already live in and keeps chat, tickets, code, and people context in one flow (with Cursor and MCP on my side). That’s the main benefit: less lost context when an issue spans Slack, Jira, and GitHub. It’s become a regular part of how I work.

Pros: I lead a data team and we use Willow for our agents and workflows. Setup was very easy and took a few days. It saved us cycles, and it gives us a secure way to work with a remote machine.

Cons: Adding a new MCP has to go through their team, we can't do it ourselves. I got a gift card as a thank-you for this review.

Overall: Willow does what we need for running our agents and workflows on a remote machine. It was easy to get going, and the only real gap so far is needing their team to add new MCPs for us.

Pros: Connects my AI agents to the internal tools I use for analytics.

Helps me move from Slack discussions to relevant Quix analyses with less manual copying.

Makes it easier to build repeatable workflows across systems.

Cons: Occasionally requires reconnecting or authenticating again after VPN or session changes.

Connection status and recovery could be clearer, especially when a connection drops during a longer workflow.

Overall: I'm a data team lead at Wix, and I use Willow to connect AI agents to internal tools through MCP. It lets me move from a Slack discussion to the relevant Quix analysis without manually copying all the context into the conversation. The main value for me is being able to use agents for practical analytics and recurring workflows across systems. One annoyance is having to reconnect or authenticate again after some VPN or session changes, which can interrupt ongoing work. I was offered a gift card for submitting this review.

Pros: Setup took a few minutes and I did it alone. I haven’t touched it since. When I needed partner performance data for a set timeframe, it pulled it for me, so I avoided the manual work and calculations across a lot of partners.

Cons: The one downside is that it sometimes took me a while to find the relevant connectors.

Overall: I’m a success manager at a company of about 3,000 people, and I use Willow to connect Claude to Salesforce, Gong, Slack and Google Drive. I’d recommend it to anyone in a customer-facing role, and I don’t have anyone I’d steer away from it. I received a thank-you for writing this review.

Pros: I’m a software engineer at Wix and I use Willow to connect Claude to our internal tools over MCP. My team set it up and it was really quick. I didn’t have to build my own MCP server, there’s one sign-in instead of a token per server, and I didn’t have to wait on security or IT to get access. There’s basically no upkeep on my side. One thing: a connector I wanted wasn’t there. If you’re a big company with a lot of internal tools, it’s worth a look.

Cons: A connector I wanted wasn’t there when I needed it

Overall: Amazing. Getting Claude connected to our internal tools was really quick, and there’s basically no upkeep on my end

Pros: I'm an Integration Manager on a 10-person team. I connect internal docs, MCP to my AI agent with skills and toolkits. Setup took about 10–15 minutes, self-serve, just me. In a typical week I triage and investigate customer issues from the agent instead of hopping tools using Willow AI connection. I grab the IDs I need and run them in our investigation stack from there. I also update skills, pick up org updates, and try new internal tools through the same setup.

Cons: Authentication fails sometimes. I need to be on the org VPN for things to work reliably.

Overall: Willow help with the tools that assist with the back and forth I used to do across internal systems when I was solving customer issues. I still do the same work, but triage and investigations mostly live in one agent workflow. I'd suggest it for mid-size and larger orgs that already have internal docs, MCP, and other tools. Very small orgs probably won't get as much from that kind of setup. Willow sent a thank-you for this review.

Pros: I connected it myself and it took minutes. Claude Code can reach Jira, Slack and our internal dev tools from one place, so when I investigate a bug it pulls the ticket and checks the services itself. Before, I’d have to go through Grafana dashboards and consoles and run everything by hand. Okta login is no big deal since I’m usually on the VPN already.

Cons: New servers come out a lot and I have to add each one myself. Willow points me to the right tools, but it’s still a manual step.

Overall: I’m a developer at a company with 1,000 to 5,000 people and my whole team uses it. It’s had a lot of good impact for us. I’d tell devs, UX and PMs to try it.

Pros: Connecting our GitHub code repo to Claude means the agents write help articles based on the actual button labels in the code, so I’m not guessing. An article takes a few minutes to a few hours, depending on how complex the feature is. Everyone on the team helps build the agent and adds to its skills. Willow agents are available on Slack if something doesn’t work.

Cons: There’s a desktop app and a web app, and that gets confusing. You need a VPN to log in. Every day you have to log in again and check that all the relevant apps are connected and can access each other before you start working. Setup took us a full day on our laptops.

Overall: I’m a knowledge base writer at Wix, a company of about 3,000 people. I use Willow to build agents that write help articles for new features. My team maintains the skills and IT maintains the framework. I’d recommend it for large organizations that need to connect different apps into one AI flow, so multiple teams can see the progress and base their information on it. It’s not relevant for a small team that’s just trying to work faster with AI. I received a gift card for writing this review.