Skip to main content

Connect VS Code to Willow

Get GitHub Copilot in VS Code talking to Willow.

Prerequisites​

  • VS Code 1.99 or later
  • GitHub Copilot extension enabled
  • Your organization's Willow URL (from the Connect MCP modal)

Step 1: Get Your Connection URL​

In Willow, click Connect MCP at the bottom of the left sidebar. Select VS Code from the client grid.

You'll see your connection URL and two options:

  • Add to VS Code (recommended): one-click setup. VS Code opens and prompts you to add the MCP server automatically. Skip to Step 3.
  • Copy URL: paste it manually if you prefer (see Step 2).
Willow Connect MCP modal with the Add to VS Code button highlighted

Step 2: Configure Manually​

Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P) and run MCP: Add Server....

VS Code Command Palette showing MCP: Add Server as the top option

Select HTTP (HTTP or Server-Sent Events).

VS Code prompt to choose the type of MCP server, with HTTP selected

Paste your Willow URL and press Enter.

VS Code Enter Server URL prompt with the Willow MCP URL pasted in

Enter a name for the server (e.g. Willow) and press Enter.

VS Code Enter Server ID prompt with Willow typed in

VS Code writes the entry to mcp.json and starts the server automatically.

Step 3: Authorize​

VS Code shows a notification: "The MCP Server Definition 'Willow' wants to authenticate to MCP-S." Click Allow.

VS Code notification saying the Willow MCP server wants to authenticate to MCP-S with Cancel and Allow buttons

VS Code then asks: "Do you want Code to open the external website?" Click Open.

VS Code dialog asking whether to open the external website for authentication

Your browser opens the Willow authentication page. Log in to your Willow account if prompted, then complete the authorization.

Browser showing the Willow Authorize Access screen with Visual Studio Code requesting access and an Allow button

After authenticating, the browser shows a sign-in success message and a system dialog: "Open Visual Studio Code - URL Handler?" Click Open Visual Studio Code - URL Handler.

Browser showing sign-in successful and OS dialog asking to open the VS Code URL handler

Step 4: Verify It Works​

Back in VS Code, hover over the server name in mcp.json. The status bar shows Running | 16 tools (the number will match your connected servers).

mcp.json showing Willow server with Running status and 16 tools available

Open Copilot Chat. Click the sliders icon in the chat bar to open Configure Tools.

VS Code chat bar with the Configure Tools sliders icon highlighted

In the Configure Tools panel, look for Willow or mcp-s (VS Code may display either name). Make sure it is checked, then click OK.

Configure Tools panel showing mcp-s checked with 16 tools selected

Now ask:

"List what tools you have access to in Willow MCP"

Copilot should respond with your connected Willow tools, grouped by server.

VS Code chat showing Willow MCP tools listed grouped by server including Context7 and Everything-MCP

The tools you see will depend on which MCP servers your organization admin has installed, which tools on those servers they have enabled, and what tools each MCP server exposes. Your list may look different from the one shown here.

Troubleshooting​

Copilot doesn't see any tools

  • Check that MCP is enabled: Settings → search for github.copilot.mcp
  • Confirm the server appears in Command Palette → MCP: List Servers
  • Restart VS Code

Authorization prompt doesn't appear

  • Open Command Palette → MCP: List Servers and check the status
  • Try reconnecting from the MCP server list

"type" field errors

  • Make sure "type": "http" is present in your config. Some older VS Code versions need this explicitly.

See also: General Troubleshooting

On this page