Configuring Sales Layer MCP Server in Microsoft Copilot Studio

Modified on Tue, 2 Jun at 11:48 AM

Microsoft Copilot Studio can connect to the Sales Layer MCP Server using the Model Context Protocol. This allows your Copilot agent to use Sales Layer tools to query your catalog data from a secure MCP connection.

This article explains how to configure the Sales Layer MCP Server in Microsoft Copilot Studio and how to complete the Sales Layer authorization flow.

Before you start

Before configuring the MCP Server in Copilot Studio, make sure you have:

Access to Microsoft Copilot Studio.
Permission to add a Model Context Protocol server in your Copilot Studio environment.
A Sales Layer account with access to the catalog you want to connect.
Your Sales Layer Catalog Token.

At the moment, the Catalog Token is not obtained from an API/Tokens section inside the Sales Layer PIM. To get it, contact Sales Layer Support or your Sales Layer account representative.

Recommended setup

If your version of Microsoft Copilot Studio offers Dynamic discovery for MCP servers, use that option first. Dynamic discovery lets Copilot Studio detect the OAuth configuration automatically and helps avoid manual configuration errors.

Use the following basic configuration:

Field	Value
Server name	Sales Layer MCP
Server description	MCP Server for Sales Layer PIM
Server URL	https://mcp.saleslayer.com/mcp
Authentication	OAuth 2.0

Add the MCP Server in Copilot Studio

Open Microsoft Copilot Studio.
Open the Copilot where you want to use Sales Layer data.
Go to the area where you can add tools or connect a Model Context Protocol server.
Select the option to add a new MCP server.
Enter Sales Layer MCP as the server name.
Enter MCP Server for Sales Layer PIM as the description.
Enter the server URL: https://mcp.saleslayer.com/mcp.
For authentication, select OAuth 2.0.
If Dynamic discovery is available, select it and continue with the connection.

Manual OAuth configuration

If Dynamic discovery is not available in your version of Copilot Studio, configure OAuth 2.0 manually with the following values:

Field	Value
Authorization URL	https://mcp.saleslayer.com/oauth/authorize
Token URL	https://mcp.saleslayer.com/oauth/token
Client ID	copilot-studio
Client Secret	Leave empty
Scope	Leave empty
Grant Type	Authorization Code with PKCE
Code Challenge Method	S256

★

Important: The Catalog Token is entered later in the Sales Layer authorization screen. It is not the Client ID, Client Secret, API key authentication value, or bearer token used in Copilot Studio. The Client ID is only a stable identifier for the Copilot Studio connection.

Complete the Sales Layer authorization flow

After the MCP Server has been configured, Copilot Studio starts the OAuth authorization flow.

Connect the MCP Server from Copilot Studio.
Copilot Studio opens a browser window.
A Sales Layer authorization screen appears.
Enter your Sales Layer Catalog Token.
Sales Layer validates the token.
After validation, you are redirected back to Copilot Studio.
The connection is established and the Sales Layer MCP tools become available.

Compatibility requirement

The Sales Layer MCP Server requires OAuth 2.0 with PKCE and the S256 code challenge method. PKCE stands for Proof Key for Code Exchange and is required for this connection.

If your version of Copilot Studio does not allow Authorization Code with PKCE and Code Challenge Method S256, it may not be compatible with the Sales Layer MCP Server at this time.

Reference endpoints

Use these endpoints for advanced configuration or troubleshooting:

Endpoint	URL
MCP Server	https://mcp.saleslayer.com/mcp
OAuth Authorization	https://mcp.saleslayer.com/oauth/authorize
OAuth Token	https://mcp.saleslayer.com/oauth/token
OAuth Discovery	https://mcp.saleslayer.com/.well-known/oauth-authorization-server
OAuth Protected Resource	https://mcp.saleslayer.com/.well-known/oauth-protected-resource

Test the connection

Once the server is connected, open your Copilot and check that the Sales Layer MCP tools are available. You can test with a simple prompt such as:

What Sales Layer tools are available?

You can also ask a catalog-related question, for example:

Show me a summary of the product catalog.

If your connection is configured with a read-only access profile, Copilot can query catalog data but cannot make changes to your Sales Layer catalog.

Troubleshooting

Issue	Cause	What to do
invalid_token	The Catalog Token was used as an API key or bearer token in Copilot Studio.	Change authentication to OAuth 2.0 and enter the Catalog Token only in the Sales Layer authorization screen.
PKCE or S256 options are not available	Your Copilot Studio version may not support the required OAuth configuration.	Check whether your version supports Authorization Code with PKCE and Code Challenge Method S256.
The authorization window does not open	The browser popup may be blocked, or the connection may not have started correctly.	Allow popups for Copilot Studio and try to connect the server again.
No Sales Layer tools are available	The OAuth flow may not have completed correctly.	Disconnect and reconnect the MCP Server, then complete the Sales Layer authorization flow again.

Best practices

Use Dynamic discovery whenever it is available in Copilot Studio. If you need to configure OAuth manually, review every field before connecting.

Keep your Sales Layer Catalog Token secure. Enter it only in the Sales Layer authorization screen, and never paste it into Client ID, Client Secret, API key, or bearer token fields.

Start with a read-only connection when you only need Copilot to query or analyze catalog data. Use full access only when the Copilot is intended to perform write operations and the users understand the impact of those actions.