Skip to main content

Some screenshots show mcp-s.com, which some existing organizations still use. New organizations use withwillow.ai. Copy the URLs shown in your own organization.

MCP Servers

The MCP Servers page is your organization's inventory of MCP integrations. Open it from Build > MCP Servers.

Each row in the table represents one MCP server. Clicking a row opens the server's edit page, where the full configuration lives across six tabs: Overview, Setup, Tools, Resources, Prompts, and Settings. The list page itself is just the inventory. The tabs are where you actually configure and manage each server.

Willow MCP Servers table showing server rows with Name, Transport, Content, Groups, Owners, Updated, and Status columns, plus the Add MCP Server button

Scopes​

Tabs at the top of the page switch between scopes, each showing a count:

ScopeContents
Org MCPsThe MCP servers your organization manages. This is the inventory described below.
User MCPsPersonal MCP servers your users added. The tab appears only when the User MCP Policy is Needs Approval or Allow. See User MCPs.
Discovered MCPsMCP servers found running on your users' devices that your organization does not manage. See Discovered MCPs.

Table columns​

The table supports search and sortable columns.

ColumnDescription
NameDisplay name of the MCP server. Click a row to open its edit page.
RiskOverall risk assessment score and band for the server, or a dash when it has not been assessed yet. Sortable.
Used (7d)Tool calls to the server in the last 7 days.
Auth errors (7d)Calls that failed on authentication in the last 7 days, or 0. Hover for the breakdown, or select the number to open the server's analytics. Sortable.
AuthWhether authentication is configured for the upstream connection.
TransportConnection type: Built-in for a Willow connector, or HTTP or STDIO for a server you configured yourself.
ContentTool count and whether prompts or resources are enabled for the proxy.
GroupsGroups whose members can access this server through the gateway.
OwnersAdmins responsible for the server in the dashboard.
CreatedWhen the server was added.
UpdatedLast time the server configuration changed.
StatusCurrent lifecycle state.

A download icon above the table exports the current list as CSV.

MCP Servers list with the Risk column showing per-server scores and bands, alongside Groups, Owners, and Status

Server statuses​

New servers start as draft. A draft server is visible to admins in the dashboard but doesn't appear to end users through the gateway. No tool calls reach it regardless of group membership. Once you've finished setup, publishing changes the status to active and makes the server available to users in connected groups. The Publish button sits in the top right of the server's edit page.

StatusMeaning
draftVisible to admins only. Not accessible through the gateway.
activeLive. Users in connected groups can reach it through the gateway.

Editing an active server doesn't change what users get. Willow keeps the changed name, description, logo, tools, request settings, proxy configuration, and conditions as Draft changes, and everyone keeps the published version until you select Publish draft (or Discard draft to drop them). Only groups with Show draft MCPs turned on receive the draft. Authentication settings are the exception: they always apply to the live server. Your own tool test in the dashboard runs the pending changes, so a call can succeed there while a user or background agent that gets the published version still fails. If that happens, look for the Draft changes badge beside the status and publish or discard it.

Discovered MCPs​

The Discovered MCPs tab lists MCP servers that Willow found running on your users' machines but that your organization does not manage. They come from AI Discovery, so the tab is populated by the scan agent rather than by anything you configure here.

ColumnDescription
MCP ServerThe discovered server's name.
AI AgentsWhich AI clients were seen using it.
DevicesHow many devices it was found on.

These are the servers counted as shadow in AI Discovery's governance figures. Bringing one under management is what moves your % governed up.

To adopt one, select the + at the end of its row. Willow opens Create Custom MCP pre-filled with the configuration it discovered, for example an npx command and its arguments for a stdio server. Review it, set a name and slug, then create the integration. From that point the server is an organization MCP server like any other, subject to your groups, guards, and tool enablement.

User MCPs​

A personal MCP server works only for the user who added it. Under the Needs Approval policy, a new one shows Needs Approval in its Status column with an Approve button, which appears for admins who can publish MCP servers.

To make a personal server available to other people, open its row menu on the User MCPs tab and select Promote to Org. Confirm the name, description, and slug, and Willow creates a published organization copy; if the slug is already taken, it appends a number. The user keeps their original. Promoting does not give anyone access to the copy, so assign it to groups afterwards.

Row actions​

Open the three-dot menu on any row to act on a server without opening its edit page.

ActionResult
EditOpens the MCP server edit page.
Copy connection URLCopies the server's gateway connection URL. Not shown for a server that runs locally.
Promote to OrgShown on User MCPs rows only. Creates an organization copy of the personal server; see User MCPs.
DuplicateCreates Copy of [original name] with the same configuration.
Download MCPBDownloads the server as an MCP bundle. Shown only on on-prem and hybrid deployments.
DeleteOpens a destructive confirmation. Deleting cannot be undone. Not shown while the server is active.
Delete Integration confirmation modal with Cancel and Delete actions

What to do next​