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, plugins, 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 12 of its 13 tools and holds back Delete User Toolkit.
Available tools
Thirteen tools, all scoped to whoever is calling.
Read-only
List User MCP Servers, List User Toolkits, List User Commands, List User Skills, List User Plugins, Check Connection, Get Auth URL
List User MCP Servers, List User Skills, and List User Plugins take a search argument with one or more keywords, so a user can ask their AI client to find what helps with a task. A match on any keyword counts: against name, slug, description, and tool names for MCP servers, and against name, slug, description, and tags for skills and plugins. List User MCP Servers also takes include_tools to return each server's enabled tools, and List User Plugins lists the plugins the user can install.
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
Create User Skill and Update User Skill run the same security review as the Connect portal: the guard checks and the AI risk scan, including bundled scripts and references. The response carries a review.status of published, draft, or pending, with a message the AI client can relay. A pending skill stays hidden until an admin approves it from the Skills page, and editing a skill that is pending or rejected sends it back to that queue. A skill blocked by a guard policy is refused with a 403. Both tools also return a 403 when your organization has turned off Allow adding skills in End-User Settings.
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