G2

Karin W.

Engineer

Enterprise (> 1000 emp.)

11/9/2026

"Took an on-call alert from half a day to an hour"

5/5

What do you like best about Willow AI Governance Control Plane?

All my MCPs are in one place and they work from Claude Code. I use Slack, GitHub, Google Drive, Grafana and some internal MCPs for our infra tools, a few times a day. Adding a new internal MCP is easy, and I've never had to remove one. Re-auth got a lot better recently, and day to day the work is smooth. I don't really think about it. Review collected by and hosted on G2.com.

What do you dislike about Willow AI Governance Control Plane?

Login is two steps for me, Google first and then SSO. I'd rather it be one. I also still have to re-authenticate every couple of weeks or so. It's much better than it was, but it's not zero. Review collected by and hosted on G2.com.

What problems is Willow AI Governance Control Plane solving and how is that benefiting you?

It cuts out the jumping between tools. A typical flow for me is to read an issue from Slack, create a ticket, implement the fix and open a PR, all from the same agent session. The best example was on on-call. An alert came up in our channel and I investigated it with a skill that calls the Slack and Grafana MCPs through Willow. Then I had my agent write the fix, open the PR with the GitHub MCP, and reply on the Slack thread with the Slack MCP. That took me 30 minutes to an hour. Investigating it by hand would have taken me half a day. Review collected by and hosted on G2.com.

Current UserValidated ReviewerIncentivizedSource: Seller invite