Universal Willow URL
Every Willow organization can be reached through one shared URL:
https://mcp.withwillow.ai/mcp
The universal URL doesn't name an organization. You choose yours when you sign in, so the same URL works for everyone. It's the URL Willow's listing in the Claude Connectors Directory uses, and you can paste it into any AI client that supports remote MCP servers with OAuth.
Organizations hosted in the EU use https://mcp.eu.withwillow.ai/mcp.
Universal URL or your organization's URL
Both URLs reach the same tools, with the same permissions and audit logging.
| Universal URL | Your organization's URL | |
|---|---|---|
| URL | https://mcp.withwillow.ai/mcp | https://yourorg.withwillow.ai/mcp |
| Organization | Picked when you sign in | Part of the URL |
| Best for | Directory listings, shared setup guides, people who don't know their org's URL | Setups your admin hands out from the Connect MCP modal |
If your admin gave you a URL from the Connect MCP modal, keep using it. The universal URL is there for when one URL has to work for everyone.
How signing in works
- Add
https://mcp.withwillow.ai/mcpto your AI client. For Claude, see Connect Claude Web to Willow. - When the client opens your browser, Willow asks you to Choose your organization. Enter your organization identifier: the first part of your Willow gateway URL, for example
acmeinacme.withwillow.ai. - Willow sends you to your organization's usual sign-in, such as SSO, Google, or email.
- After you sign in, the browser returns you to your AI client and the tools load.
Willow remembers the organization you picked, so it's filled in the next time you connect.
No Willow account yet
Select Sign up under the organization field. This opens app.withwillow.ai/signup, where you can create an account with Google, GitHub, or email. When sign-up finishes, Willow returns you to the connection you started, with your new organization already filled in. You don't need to start over in your AI client.
If you sign up with email, open the verification link in the same browser you started in, within an hour. Willow can only return you to the connection from that browser.
Which tools you get
A connection to https://mcp.withwillow.ai/mcp doesn't name a toolkit or MCP server. In that case, your admin's Default MCP setting decides what's listed:
- All MCPs: every tool from every MCP server you can access, optionally capped.
- Dynamic MCP: a few search and execute tools. Your AI client looks up the tools it needs as it goes.
- Default Toolkit: only the tools in one toolkit your admin picked.
To always get a specific toolkit or MCP server, add it to the URL:
| To connect to | Use |
|---|---|
| One toolkit | https://mcp.withwillow.ai/mcp/toolkit/<toolkit-slug> |
| One MCP server | https://mcp.withwillow.ai/mcp/mcp/<mcp-slug> |
The query-parameter forms (?toolkit=<slug> and ?mcp=<slug>) work too. A toolkit or MCP named in the URL always wins over the Default MCP setting.
Troubleshooting
"We couldn't find that organization"
- Check the identifier against your Willow gateway URL. It's the part before
.withwillow.ai. - If your organization uses a custom gateway domain, ask your admin for the identifier.
"That organization isn't reachable through the universal endpoint"
- Your organization is served from its own gateway, for example a self-hosted or custom-domain gateway. Use the URL from the Connect MCP modal instead.
Sign-up didn't bring me back to my AI client
- Start the connection again from your AI client. If you're already signed in, you go straight to the organization picker.
- If you verified your email in a different browser, or more than an hour later, Willow can't link it to the original connection.
I see different tools than I expected
- Your admin's Default MCP setting may list a toolkit or the Dynamic MCP tools instead of every MCP server. Name a toolkit or MCP server in the URL to get exactly that set.
See also: General Troubleshooting
Related
- Connection Methods: MCP Gateway vs Dynamic vs CLI
- Connect Claude Web to Willow
- All AI Clients