Skip to main content
Use this path for Microsoft Copilot Studio agents. Consumer Microsoft Copilot and Google-style answer surfaces are not normal user-configurable MCP clients.
Copilot Studio MCP access is mediated by Power Platform connector and connection flows. Lightsage MCP does not support OAuth today. Connect directly only if your connector can send the X-Lightsage-Api-Key header without exposing the key to end users.
1

Get your Lightsage API key

Open the Lightsage dashboard and copy your API key.Use the key only where your Copilot Studio connector setup supports API-key authentication. Do not paste it into shared connector docs, screenshots, or public repositories.
2

Connect the Lightsage MCP server

In Copilot Studio, open your agent and use the MCP onboarding flow to connect an existing MCP server.Set the server URL to:
When the connector asks for authentication, use the header name X-Lightsage-Api-Key with your Lightsage API key if custom API-key headers are supported. If your tenant requires OAuth or another auth model, it cannot connect directly to the hosted Lightsage MCP endpoint today. Use a private server-side wrapper that injects the Lightsage API key.
3

Add Lightsage tools to the agent

Open the agent’s Tools page, choose Add a tool, select Model Context Protocol, and select the Lightsage MCP connector.Keep the default tool selection first. After the server is connected, turn off tools the agent does not need.
4

Verify the agent

Publish or test the agent, then run a read-only prompt:
If tool calls fail with 401, confirm the connector is sending X-Lightsage-Api-Key on every request.
See the Copilot Studio MCP overview and add MCP tools to an agent.