Skip to main content
Qwairy works with GitHub Copilot in Visual Studio Code as a remote HTTP MCP server. You add the server to VS Code, sign in with OAuth, and ask Copilot Chat questions about your brands. The connection is read-only. This page covers GitHub Copilot in VS Code. It does not cover Microsoft 365 Copilot or Copilot Studio.

​
Before you start

  • Access to a Qwairy team on a Starter plan or higher. You can connect before monitoring has run. Queries return data once a live brand has generated responses.
  • Visual Studio Code with the GitHub Copilot extension and a GitHub Copilot plan
  • On Copilot Business and Enterprise, an administrator must enable the MCP servers in Copilot policy: under Settings > Copilot > Policies for an organization, or AI controls > MCP for an enterprise. An enterprise policy can override the organization setting. Without it, Copilot cannot use MCP servers for those members.

​
Connect Qwairy to GitHub Copilot

1

Add the server

Open the Command Palette and run MCP: Add Server. Choose an HTTP server and enter:
Enter qwairy as the server name. Choose Global for all workspaces or Workspace for the current repository, and trust the server when VS Code asks.The equivalent configuration in .vscode/mcp.json (workspace) or your user mcp.json (global) is:
2

Sign in to Qwairy

Open mcp.json and click Start above the qwairy entry. VS Code opens the Qwairy sign-in page in your browser. Sign in with the Qwairy account that has access to your brands and approve the access.
3

Return to VS Code

Return to VS Code. The qwairy server is running once sign-in completes. The actions above the entry in mcp.json let you stop or restart it.

​
Check that the connection works

First confirm the server in VS Code: open the Command Palette, run MCP: List Servers, and check that qwairy is listed and running. Then open Copilot Chat in a mode that can use tools and send:
Copilot should call Qwairy’s list_brands tool and display the accessible brands. Approve the tool call if Copilot asks. A general answer without a tool call does not confirm the connection.

​
Troubleshooting

​
Copilot does not use Qwairy

On Copilot Business and Enterprise, ask an organization owner to enable the MCP servers in Copilot policy. Then run MCP: List Servers and check that qwairy is running, and that its tools are enabled in the Copilot Chat tool picker.

​
The server does not start or needs authentication

Run MCP: List Servers, select qwairy, and choose Show Output to read the error. Choose Restart Server to sign in again. Check that the URL is https://mcp.qwairy.co without /mcp and that the JSON is valid.

​
Authorization fails

Sign in with the Qwairy account that has access to your brands, and check that its team is on a Starter plan or higher. See general troubleshooting.

​
Official documentation

Policies, plans, and interface labels are maintained by GitHub and Microsoft. See Extend Copilot Chat with the Model Context Protocol and Manage and troubleshoot MCP servers in VS Code. Procedure checked against vendor documentation on October 22, 2026.

​
Next steps