Connecting Sales Layer MCP Server to Cursor

Modified on Tue, 2 Jun at 12:21 PM

Cursor can connect to the Sales Layer MCP Server so its AI agent can use Sales Layer tools while you work in the editor. This is useful for technical teams that want to query, analyze, or validate Sales Layer catalog data from an AI-first development environment.

This article explains how to add the Sales Layer MCP Server in Cursor, complete the Sales Layer authorization flow, and test that the connection is working.

Note: Cursor versions and menu names may vary. If you do not see the same options, update Cursor and check whether MCP support is enabled in your workspace.

Before you start

Before connecting the Sales Layer MCP Server to Cursor, make sure you have:

Cursor installed on your computer.
A Cursor version that supports MCP servers.
Access to the Sales Layer catalog you want to query.
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.

Warning: Do not paste your Sales Layer Catalog Token as a bearer token or API key in Cursor. For the remote MCP Server, the Catalog Token is entered in the Sales Layer authorization screen during the connection flow.

Choose the access mode

Use the access mode that matches what you want Cursor to do with your Sales Layer catalog.

Mode	Server URL	Use it when
Default remote connection	https://mcp.saleslayer.com/mcp	You want Cursor to connect through the standard Sales Layer MCP endpoint.
Read-only	https://mcp.saleslayer.com/onlyread/mcp	Cursor only needs to query, inspect, or analyze catalog data.
Full access	https://mcp.saleslayer.com/full/mcp	Cursor needs to create or update Sales Layer data through MCP tools.

For most first-time setups, start with Read-only. Use Full access only when your workflow is designed to modify catalog data and users understand the impact of those actions.

Add the MCP Server from Cursor settings

The easiest setup is to add the Sales Layer MCP Server directly from Cursor settings.

Open Cursor.
Open Settings.
Go to Tools & MCP or the MCP servers section in your Cursor version.
Click Add new MCP server.
Choose a remote HTTP or Streamable HTTP server type if Cursor asks you to select the transport.
Enter a clear server name, for example sales-layer.
Enter the Sales Layer MCP Server URL.
Click Connect or Save.

Use this URL for the standard remote setup:

https://mcp.saleslayer.com/mcp

Complete the Sales Layer authorization flow

After saving the MCP Server, Cursor should start the authorization flow in your browser.

When the browser opens, wait for the Sales Layer authorization screen.
Select the access profile if the screen asks you to choose one. Use Read only unless Cursor needs to update catalog data.
Enter your Sales Layer Catalog Token.
Validate the token and continue.
Return to Cursor after the authorization flow finishes.

Alternative setup with mcp.json

If you prefer to manage MCP servers from a configuration file, create or edit a Cursor MCP configuration file in your project or user settings.

Add a configuration similar to this one:

{
  "mcpServers": {
    "sales-layer": {
      "url": "https://mcp.saleslayer.com/mcp"
    }
  }
}

After saving the file, reload Cursor or refresh the MCP server list. Cursor should detect the server and start the authorization flow when the server is used.

Warning: Do not add the Catalog Token to this configuration file unless Sales Layer Support specifically asks you to use a local setup. For the remote setup, authentication is completed through the browser authorization flow.

If OAuth does not start automatically

Some Cursor versions or environments may not start the OAuth flow automatically for remote MCP servers. If this happens, check whether your Cursor version supports OAuth for remote MCP servers.

If native OAuth support is not available, your technical team can use a local bridge such as mcp-remote, if approved by your organization. This option starts the remote connection from a local command and opens the browser authorization flow.

Example configuration:

{
  "mcpServers": {
    "sales-layer": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.saleslayer.com/mcp"]
    }
  }
}

This approach requires Node.js and internet access from the machine where Cursor runs. Use it only if your organization allows local command-based MCP servers.

Test the connection

After the MCP Server is connected, open Cursor Chat or Agent mode and ask a simple question to verify that Sales Layer tools are available.

For example:

What Sales Layer tools are available?

You can also ask a catalog-related question:

Show me a summary of my Sales Layer catalog.

If the connection is working, Cursor should be able to call the Sales Layer MCP tools and return information from your catalog.

Example prompts

Once the connection is ready, you can use prompts like these:

Show me the available Sales Layer tools.
Find products with missing descriptions.
Check whether any products have empty technical attributes.
Summarize the catalog structure.
Help me inspect the data returned for a specific product reference.

If you are using read-only access, Cursor can query and analyze Sales Layer data, but it cannot create or update records.

Troubleshooting

Issue	Likely cause	What to do
MCP settings are not visible in Cursor	Your Cursor version may not support MCP, or MCP may not be enabled.	Update Cursor and check whether MCP support is available in your environment.
The browser authorization screen does not open	The OAuth flow did not start, popups are blocked, or the Cursor version does not support remote MCP OAuth.	Allow browser popups, reconnect the server, or use an approved local bridge such as mcp-remote.
invalid_token	The Catalog Token was used as a direct bearer token instead of being entered in the Sales Layer authorization screen.	Remove any bearer token configuration and complete the OAuth authorization flow again.
No Sales Layer tools are available	The server was not loaded, or the authorization flow did not finish correctly.	Reconnect the MCP Server and restart Cursor if needed.
Cursor can query data but cannot update it	The connection is using read-only access.	Use full access only if Cursor must perform write actions and your organization allows it.
mcp-remote does not run	Node.js or npx may not be available on your computer, or local command execution may be blocked.	Ask your IT team to confirm whether local MCP command servers are allowed.

Best practices

Start with read-only access when you only need Cursor to inspect, query, or analyze catalog data.

Use full access only for trusted technical workflows that are expected to create or update Sales Layer data.

Keep your Catalog Token secure. Do not paste it into configuration files, screenshots, support tickets, or shared code repositories.

After connecting the MCP Server, test it with a simple prompt before using it for real catalog work. If you change the server URL, access mode, or authentication flow, restart Cursor and test again.