Willow User
Willow User exposes Willow's User API as an MCP server. Where Willow Admin manages the organization, this one is scoped to the calling user: their own MCP servers, toolkits, commands, skills, and integration connections.
It is the connector to reach for when you want people to manage their own Willow setup by asking their AI client, rather than switching to the Connect portal.
Add it
- Open Build > MCP Servers > Add MCP Server.
- Search for
Willow Userand hover the card. - Select Use.
- Review the risk level and the tool list, then select Create.
The connector is scored Medium Risk by default. At that level Willow enables 11 of its 12 tools and holds back Delete User Toolkit.
Available tools
Twelve tools, all scoped to whoever is calling.
Read-only
List User MCP Servers, List User Toolkits, List User Commands, List User Skills, Check Connection, Get Auth URL
Check Connection and Get Auth URL are the useful pair for self-service connection troubleshooting: the first reports whether the caller has authorized a given server, and the second returns the URL they need to visit to authorize it.
Create and update
Create User Toolkit, Update User Toolkit, Create User Skill, Update User Skill, Submit Issue
Delete
Delete User Toolkit, classified high risk and excluded at the default Medium Risk level.
Recommendations
This connector is safe to give a broad audience, because every tool is scoped to the caller. A user cannot read or change another person's toolkits through it. That makes All Users a reasonable connected group, unlike Willow Admin.
Pair it with the Connect portal rather than replacing it. Users still need the portal to complete OAuth authorizations; Get Auth URL hands them the link but cannot authorize on their behalf.
Related
- User API reference: the same operations as HTTP endpoints
- Willow Admin: the organization-wide counterpart
- Toolkits: what users are creating and editing through these tools