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.

End-User Settings

End-User Settings controls what people outside the admin app see and can do in the Connect portal. Open Admin > Settings > End Users. End-User Settings has three sections:

SectionSettings
MCP AccessMCP Connection Format, Default MCP, User MCP Policy, Dynamic MCP & Willow CLI, Approvals Inside the Chat
Connect PortalCompany Policy, Hide Integration Stats, Sidebar Pages
Skills, Plugins & AgentsAdding Skills & Plugins, AI Search, Custom Skill Command, Custom Plugin Install Command, Agent Policies

Changes here apply to the whole organization.

End-User Settings on the MCP Access section, with the MCP Connection Format, Default MCP, User MCP Policy, and Dynamic MCP & Willow CLI cards

MCP Connection Format​

Chooses how MCP identifiers are passed to the server in the connection details users copy. The card shows the current format. Select Edit to pick a format.

FormatResulting connection
Query Parametershttps://your-org.withwillow.ai/mcp?mcp=my-mcp
Path Parametershttps://your-org.withwillow.ai/mcp/my-mcp
Headershttps://your-org.withwillow.ai/mcp with { headers: { "X-MCP": "my-mcp" } }

Pick the format your users' AI clients handle best. Some clients accept a URL but provide no way to set custom headers, which rules out the Headers format for them.

MCP Connection Format dialog with Query Parameters, Path Parameters, and Headers options, each previewing the resulting connection string

Default MCP​

Chooses what users get when they connect without naming a toolkit or MCP server. Examples include https://your-org.withwillow.ai/mcp with no ?mcp= or ?toolkit=, and the universal URL https://mcp.withwillow.ai/mcp, which Willow's Claude Connectors Directory listing uses. The card shows the current mode, for example All MCPs. Select Edit to pick a mode.

ModeWhat users get
All MCPsEvery tool from every MCP server the user can access. Organizations created before Dynamic MCP became the default stay on this until an admin changes it.
Dynamic MCPFive discovery tools instead of the whole catalog: search_tools, get_mcp_servers, get_mcp_tools, get_tool_details, and execute_tool. The AI client looks up the tools it needs and runs them through execute_tool.
Default ToolkitOnly the tools in the toolkit you pick.

New organizations start on Dynamic MCP, so the universal URL lists the same five tools in every AI client.

A toolkit or MCP server named in the connection always wins over this setting, whether it's in the path, the query, or a header. The Willow CLI ignores this setting and always gets every tool the user can access, since it has its own tool search. Changes reach connected clients within about 30 seconds, and clients pick up the new tool list the next time they fetch it.

All MCPs: Max tools​

Optionally caps how many tools are listed, from 1 to 10,000. When the cap applies, the most recently used tools are listed first. Leave it blank to list every tool.

A cap helps when a large catalog runs into an AI client's limit on how many tools one connection can list.

Dynamic MCP​

Best for organizations with large catalogs, or for users who work across many systems. The AI client's context only holds the five discovery tools, not every tool definition. The tradeoff is an extra lookup step before each new tool is used.

Default Toolkit​

Pick a toolkit from the list, or select New Toolkit to create one without leaving the panel. You can't save the setting without a toolkit.

The panel warns you when:

  • The toolkit no longer exists: it was deleted or renamed. Pick another one.
  • The toolkit has no MCP servers: users get no tools until you add some to the toolkit.

Users who can't access the toolkit, or any of its MCP servers, get an error when they connect without naming a toolkit or MCP server. Make sure the groups that use the default connection can access the toolkit.

User MCP Policy​

Controls whether end users can connect their own MCP servers alongside the ones you provide. The card shows the current policy, for example None. Select Edit to change it.

This has its own reference page. See User MCP Policy.

Dynamic MCP & Willow CLI​

Chooses whether end users can use Dynamic MCP (Willow Mesh) and the Willow CLI in Connect. The card has two switches.

SwitchWhat it controls
Support Dynamic MCPShows the Willow Mesh server in the Connect portal and lets Default MCP use Dynamic MCP. When it is off, Dynamic MCP is not offered as a Default MCP, and saving the switch off while Default MCP is set to Dynamic MCP resets Default MCP to All MCPs.
Support Willow CLIShows the Willow CLI option in the Connect MCP dialog. On unless you turn it off.

Approvals Inside the Chat​

When a tool call needs approval, shows Approve and Decline buttons inside AI tools that support MCP Apps, like Claude, so people can answer without leaving the chat. Other AI tools keep getting a link to the approval page. Off by default, so every AI tool gets the link.

Company Policy​

Shows a policy that users accept before they can use Willow. Users see it the first time they sign in to Willow, from the portal or any MCP client. They scroll to the end and accept it, and sign-in completes. The Users list shows who accepted.

Company Policy card with the Require users to accept the policy switch, a Title field, and a Policy (Markdown) editor with Write and Preview tabs
  1. Turn on Require users to accept the policy.
  2. Enter a Title, for example AI Tools Acceptable Use Policy.
  3. Write the policy in Policy (Markdown). Select Preview to see how it renders, and Write to go back to editing.

Hide Integration Stats​

Hides integration usage statistics from end users in the Connect portal. Off by default, so users see the stats.

Adding Skills & Plugins​

Controls whether end users can add their own content in the Connect portal. Allow adding skills and Allow adding plugins are separate switches. They cover creating content manually, uploading a file, and importing from GitHub.

Use these controls to manage content creation. To control whether the Skills or Plugins page appears in the portal sidebar, use Sidebar Pages.

Adding Skills & Plugins with separate Allow adding skills and Allow adding plugins switches

Adds an AI search box to the Skills and Plugins pages in the Connect portal. Users describe what they want to do and get the best matches from the catalog they can see. Turn on Enable AI search for skills and plugins and save. Skills are also tagged when they are scanned, which improves the results. The card shows On or Off.

Until an admin saves a choice here, AI search follows the AI search beta, so it is off for organizations without the beta. A choice saved here always wins.

Custom Skill Command​

Overrides the default skill install command with a custom JSONata expression. Off by default, which uses Willow's built-in command.

Custom Plugin Install Command​

Overrides the default plugin install command with a custom JSONata expression, set per platform. Off by default.

Agent Policies​

Manages Claude Code policies and deploys them to developer machines organization-wide via MDM. Select Manage to open the editor.

This has its own reference page. See Claude Code Policy.

Chooses which pages are visible to end users in the Connect portal sidebar, for everyone or for selected groups. The Sidebar Pages card lists each page with its own switch. Chat, Commands, and Background Agents are off by default, and the rest are on. The screenshot below shows Commands and Background Agents turned off, which removes them from the portal sidebar.

Sidebar Pages card with switches for MCP Servers, Skills, Commands, Toolkits, Chat, Background Agents, Plugins, and Analytics, each turned-on page showing Everyone, and Commands and Background Agents turned off
PageWhat users get
MCP ServersBrowse and connect MCP servers.
SkillsThe skills catalog.
CommandsThe command library.
ToolkitsCurated toolkits.
ChatIn-app chat.
Background AgentsBackground agents.
PluginsThe plugin marketplace.
AnalyticsUsage analytics.

Turning a page off hides it from the sidebar for everyone in the organization. It also leaves the page out of the Connect home page: its cards, sections, search suggestions, and links no longer appear there.

To show a visible page to only some users, select the groups button beside its switch (it reads Everyone until you pick groups) and choose the groups that should see it. Users who are in none of those groups see the page as turned off, and the card on this page reports how many pages are limited to groups. Limiting a page to groups only narrows it: a page you have turned off stays hidden for everyone.

The page is not blocked outright. A user who opens its URL directly sees a "This feature is currently disabled" notice with a link back home. Admins still see the page, so you can preview it before you turn it on.