Skip to main content
Qwairy works with agents built in Microsoft Copilot Studio as a remote MCP server. You add Qwairy to your agent with the MCP onboarding wizard and connect your Qwairy account with OAuth. The agent can then call Qwairy’s tools to answer questions about your brands. This page covers Copilot Studio agents powered by the standard harness, which use the MCP onboarding wizard. For an agent created in the new Microsoft Copilot experience (preview), Microsoft documents a separate path from the Build tab in Add an MCP server to your agent (Microsoft Copilot). For GitHub Copilot in VS Code, see Connect GitHub Copilot.

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.
  • A Copilot Studio agent that you can edit, with generative orchestration turned on. Copilot Studio agents use MCP servers only with generative orchestration, which the Copilot Studio for Teams plan included in some Microsoft 365 subscriptions does not offer.
  • An agent that authenticates its users. Keep the default Authenticate with Microsoft, or use Authenticate manually. With No authentication, the agent cannot use tools with user credentials.
  • A single-tenant agent. Copilot Studio does not support MCP tools in multitenant mode.
  • Power Platform data policies that allow the connection. Copilot Studio reaches MCP servers through Power Platform connectors, so your organization’s data policies also apply to Qwairy.

Connect Qwairy to your agent

1

Open the MCP onboarding wizard

In Copilot Studio, open your agent and go to Tools. Select Add a tool, then New tool, then Model Context Protocol.
2

Enter the server details

Fill in the required fields.The agent reads the description to decide when to call Qwairy. Adapt it to the questions your agent should answer.
3

Choose OAuth 2.0 with dynamic discovery

Select OAuth 2.0 as the authentication type, then Dynamic discovery. Select Create, then Next.Copilot Studio finds Qwairy’s sign-in endpoints and registers itself automatically. You do not enter a client ID, a client secret, or OAuth URLs.
4

Connect your Qwairy account

In Add tool, select Create a new connection. When the Qwairy sign-in page opens, sign in with the Qwairy account that has access to your brands and approve the access. Then select Add to agent.

Check that the connection works

In Tools, select Qwairy and check that its tools are listed. Then send this message in your agent’s test pane:
The agent should call Qwairy’s list_brands tool and display the accessible brands. If the test pane asks you to connect or allow Qwairy, follow its prompt and send the message again. A general answer without a tool call does not confirm the connection. If Qwairy reports that no brands were found, the connection works, but the signed-in Qwairy account cannot access any live brand. Sign in again with the account that has access to your brands.

Share the agent with colleagues

Publish the agent again after adding Qwairy. Until you publish, people who use the agent on its channels keep the previous version. By default, the Qwairy connection uses each user’s credentials. Every person who uses the agent signs in with their own Qwairy account and sees only the brands that account can access. With Maker-provided credentials, every user queries Qwairy with your account and its access.

Troubleshooting

Copilot Studio only offers OAuth 2.0

Select OAuth 2.0 with Dynamic discovery. Qwairy’s authorization server follows OAuth 2.1, which consolidates OAuth 2.0 practices, and this Copilot Studio option completes its sign-in. You do not need an OAuth 2.1 option.

Copilot Studio asks for a client ID, a client secret, or URLs

You selected Dynamic or Manual. Go back to the authentication type and choose Dynamic discovery, which lets Copilot Studio register itself with Qwairy. If the tool already exists, remove it from the agent and add it again.

The agent answers without calling Qwairy

Check that generative orchestration is turned on for the agent and that its authentication is not set to No authentication. Then open Tools, select Qwairy, and check that its tools are listed and turned on. If the agent still answers from general knowledge or the web, check how the connection authenticates. Qwairy rejects requests without a valid Qwairy token in the Authorization header, for example from a connection created without authentication. Remove Qwairy from the agent, add it again with OAuth 2.0 and Dynamic discovery, and create a new connection.

The connection is blocked

A Power Platform data policy can block the connector that Copilot Studio created for Qwairy. Ask your Power Platform administrator to allow it in the environment that hosts your agent. If the connector is allowed but Qwairy stays unavailable for some users or groups, an organization policy may limit the tool. A Microsoft 365 administrator can review the access request in the Microsoft 365 admin center under Agents > Tools > Requests.

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. If the problem persists, remove Qwairy from the agent, add it again, and create a new connection. See general troubleshooting.

Official documentation

Interface labels, plans, authentication, and data policies are maintained by Microsoft. See Connect your agent to an existing Model Context Protocol (MCP) server, Extend your agent with Model Context Protocol, and Configure user authentication in Copilot Studio. Procedure checked against Microsoft’s documentation on November 20, 2026.

Next steps