Connection Methods
Most connections to Willow go through your organization's gateway URL:
https://yourorg.withwillow.ai/mcp
What your AI can reach depends on whether the connection names a single MCP server, a toolkit, or neither. Where you open the Connect MCP dialog decides which one you get.
Everything available to you
Click Connect MCP at the bottom of the sidebar. The dialog generates a connection for the plain gateway URL, with no server or toolkit named.
A connection like this gives your AI whatever your admin has set as the default, usually every MCP server available to you. It suits exploratory or cross-system work, where you want the AI to draw on whichever system is relevant.
One MCP server
On the MCP Servers page, click Use on a server you've connected. The same dialog opens with the server named at the top (for example, MCP: github), and the URL points at that server only:
https://yourorg.withwillow.ai/mcp?mcp=github
Your AI only ever sees that server's tools. If you connect to GitHub, you get GitHub tools, and nothing else appears unless you add a second connection.
This predictability is useful for focused work such as reviewing pull requests, creating tickets, or searching documentation. With bounded access, the AI behaves more consistently, because it knows exactly what it can do in that session.
To reach a few servers in one connection, list their slugs separated by commas, for example ?mcp=github,slack. The X-MCP header takes the same list (X-MCP: github,slack). Your AI sees only the tools of the servers you name, and only those you have access to.
When a connection names a single server, AI tools that show server logos (for example Codex's sidebar) show that server's logo. A logo your admin set on the server in Willow always wins. When the server has no logo in Willow, Willow saves the logo the server itself reports the next time its tools sync.
A toolkit
On the Toolkits page, click Use on a toolkit. The toolkit's page opens in two steps: Authenticate your MCPs, then Connect. The connection points at the toolkit:
https://yourorg.withwillow.ai/mcp?toolkit=my-toolkit
Your AI gets exactly the tools, prompts, and resources in that toolkit. See Toolkits.
The examples above use query parameters, which is the default. Your admin can switch the organization to path parameters (/mcp/github) or a header (X-MCP: github). The dialog always shows the format your organization uses, so copy the URL or config from there.
A local server
Some servers run on your computer. They show a Local badge, and Use offers STDIO only. See Local MCP servers.
Universal URL
https://mcp.withwillow.ai/mcp reaches every organization through one URL. You pick your organization when you sign in. It's the URL in Willow's Claude Connectors Directory listing, and it suits setup guides that have to work for everyone. Unless you name a toolkit or MCP server in the URL, your admin's Default MCP setting decides which tools you get. See Universal Willow URL.
Willow CLI
Select Willow CLI in the dialog to call Willow tools from a terminal or a script instead of a chat client. The CLI also installs a skill into the AI agents on your machine so they can find and call your tools on their own. When you open the dialog from a server, turn on Scope to this MCP only to limit the CLI to that server.
See the Willow CLI reference for the full list of commands.
If you're unsure where to start, click Use on the server you need most and add that connection to your AI client. You can add more connections later.
Set up your AI client
Once you have a URL, follow the guide for your specific client.