Connect Claude Desktop to Willow
Connect the Claude Desktop app to your Willow workspace using the Willow extension. Once installed, all the tools, resources, and prompts your organization has configured are available directly inside Claude.
Unlike the HTTP clients, Claude Desktop connects through a downloadable .mcpb extension (an MCP Bundle) that you drag into Claude's settings.
Prerequisites
- Claude Desktop installed (macOS or Windows)
- Node.js 18 or newer installed system-wide
- Your organization's Willow Gateway URL (e.g.
https://yourorg.withwillow.ai) — find it in the Connect MCP modal
Step 1: Download the Extension
Download the Willow extension bundle:
⬇ Download the Willow extension (willow.mcpb)
The file downloads as willow-<version>.mcpb. Save it somewhere easy to find, like your Downloads folder.
Your admin may distribute a pre-configured build instead. If they sent you a
.mcpbfile directly, use that one — it may already have your organization baked in.
Step 2: Install in Claude Desktop
- Open Claude Desktop.
- Go to Settings → Extensions.
- Drag and drop the
.mcpbfile onto the window (or click Advanced settings → Install extension and browse to it). - Claude shows the extension details. Click Install.
Step 3: Configure
During install (or later from the extension's settings), you can set:
| Field | Description |
|---|---|
| Gateway URL | Your Willow gateway URL, e.g. https://yourorg.withwillow.ai. Required unless your admin baked it into the build. |
| Toolkit | (optional) Scope the extension to a single toolkit by its slug. |
| MCP Server | (optional) Scope the extension to a single MCP server by its slug. |
Leave Toolkit and MCP Server empty to get everything you're permitted to access. Click Save and make sure the extension is toggled on.
Step 4: Authenticate
The first time Claude starts the extension, it opens your browser to log in to Willow.
- Log in to Willow if prompted.
- Willow shows an Authentication Successful page.
- Return to Claude Desktop — your token is cached automatically for future sessions.
Step 5: Verify It Works
Start a new conversation in Claude Desktop and ask:
"List what tools you have access to in Willow MCP"
Claude should respond with the tools from your Willow workspace.
The tools you see depend on which MCP servers your organization admin has installed, which tools they have enabled, and what each server exposes. Your list may look different from someone else's.
The list also includes two support tools,
authenticateanddoctor, even after you have signed in. Claude Desktop shows the tool list it saw last, so the extension keeps them listed.
Troubleshooting
Extension not showing up after install
- Fully quit and reopen Claude Desktop.
- In Settings → Extensions, confirm the Willow extension is toggled on.
"node not found" / server fails to start
- Ensure Node.js 18+ is installed system-wide and on your
PATH(node --version).
Tools don't load, or Claude errors once the extension is on
- Claude Desktop struggles when the extension exposes too many tools. Open the extension's settings and set Toolkit (or MCP Server) to scope it down. Pick a toolkit your team already uses, or create your own with just the tools you need.
Tools you just added or changed don't show up
- Claude Desktop reads the tool list when it starts and does not refresh it while it runs, so a toolkit or MCP server your admin changed afterwards stays out of date. Quit Claude Desktop completely (Cmd+Q on Mac, or quit it from the system tray on Windows; closing the window is not enough), reopen it, and start a new chat.
Claude says Willow is only partly connected, or lists only authenticate and doctor
- Claude Desktop cannot refresh the tool list inside a conversation that started before the tools loaded, for example when your VPN was off or your sign-in had expired. Signing in again does not change that conversation. Start a new conversation. If the tools are still missing, quit Claude Desktop completely and reopen it, as in the previous item.
Claude says it "couldn't reach MCP-S"
- MCP-S is the old name of the extension, so Claude is still opening an old install. Open Settings → Extensions, turn off or remove the MCP-S entry, then install the current Willow extension from Step 1 (or the file your admin sent) and keep Willow switched on.
Asked to sign in again every day
- The extension keeps you signed in for as long as your admin's token lifetime allows, which is 24 hours unless they changed it. Older extension builds always expired after 24 hours regardless of that setting, so install the latest Willow extension. If you still sign in more often than your admin expects, ask them to check the access token lifetime in Willow's Security settings.
Many browser tabs open for Willow sign-in
- One sign-in is enough. Every Willow extension on the machine saves the session to the same file,
~/.willow/token.json, so once you finish signing in, the others use it. Close the extra tabs. - The latest Willow extension opens at most one sign-in tab at a time, and does not open another for two hours, even when several extensions are running. A burst of tabs usually means one of your extensions is an older build, so install the latest Willow extension for each one.
Stuck in an auth loop / can't connect
- Double-check the Gateway URL is correct (e.g.
https://yourorg.withwillow.ai). - Clear the cached token by deleting
~/.willow/token.json, then restart Claude Desktop to re-authenticate. - If signing in again never completes, or Claude is stuck waiting for a sign-in to finish and never prompts you again, install the latest Willow extension from Step 1. Older builds could leave a re-sign-in unfinished while still holding the previous session.
See also: General Troubleshooting
For Admins: Fleet Deployment
Admins can push the Willow extension to many machines at once (Iru (formerly Kandji), Jamf, Mosyle, or a custom script) instead of having each user install it manually. The extension can be pre-configured with your org, a default toolkit, and auto-enabled. Reach out to Willow support for the MDM deployment guide and install script.
Related
- All AI Clients: Setup for other clients
- Connect Claude Web: Use Willow on claude.ai instead
- Connection Methods: Everything, one server, a toolkit, or the CLI