Connecting Sales Layer MCP Server to Google Gemini

Modified on Tue, 2 Jun at 12:13 PM

Google Gemini can use MCP tools in environments that support the Model Context Protocol, such as Gemini CLI or Gemini-compatible developer tools. This allows Gemini to connect to the Sales Layer MCP Server and use Sales Layer tools to query and analyze product catalog data.

This article explains how to connect the Sales Layer MCP Server to a Gemini environment that supports MCP server configuration.

Note: The standard Gemini web or mobile app may not show an option to add custom MCP servers in every account. If you do not see an MCP, tools, extensions, or custom connector option, use Gemini CLI or another Gemini-compatible environment that supports MCP.

Before you start

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

A Gemini environment that supports MCP server configuration.
Access to the Sales Layer catalog you want Gemini to query.
Your Sales Layer Catalog Token.
For Gemini CLI setups, Node.js and npx installed if you use the mcp-remote bridge.

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 Gemini. For the remote MCP Server, the Catalog Token is entered in the Sales Layer authorization screen during the connection flow.

Choose the right setup

Google Gemini can appear in different products and developer environments. Choose the setup that matches your case:

Environment	Recommended setup	Notes
Gemini CLI	Use an MCP server configuration file. If remote OAuth is not handled directly, use mcp-remote.	Recommended for technical users.
Gemini-compatible IDE or developer tool	Add Sales Layer as a remote MCP Server if the tool exposes MCP configuration.	Menu names depend on the tool.
Gemini web or mobile app	Use only if your account shows a supported way to add custom MCP servers or external tools.	Not all accounts expose this option.

Choose the access mode

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

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

For most first-time setups, start with Read-only. Use Full access only for trusted workflows where Gemini is expected to modify catalog data.

Option 1: Connect from Gemini CLI with mcp-remote

If your Gemini CLI environment supports MCP servers through a configuration file, the most reliable setup for the remote Sales Layer MCP Server is to use mcp-remote. This bridge starts a local MCP process and connects it to the remote Sales Layer MCP Server.

Use this configuration for the standard remote endpoint:

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

For a read-only setup, use this URL instead:

https://mcp.saleslayer.com/onlyread/mcp

For a full-access setup, use this URL instead:

https://mcp.saleslayer.com/full/mcp

Note: The exact location of the Gemini MCP configuration file can vary depending on the Gemini environment and operating system. Check your Gemini CLI documentation or settings screen if you are not sure where MCP servers are configured.

Option 2: Connect through a native remote MCP URL

Some Gemini-compatible tools may support remote MCP URLs directly. If your environment offers this option, add the Sales Layer MCP Server as a remote MCP server.

Open your Gemini environment or Gemini-compatible tool.
Go to the area for Tools, Extensions, MCP Servers, or External tools.
Add a new MCP server.
Enter a clear name, for example Sales Layer MCP.
Enter the Sales Layer MCP Server URL.
Select OAuth 2.0 if the tool asks for an authentication method.
Save or connect the server.

Use this URL for the standard remote setup:

https://mcp.saleslayer.com/mcp

Complete the Sales Layer authorization flow

When the Gemini environment connects to the Sales Layer MCP Server, the authorization flow should open in your browser.

Wait for the Sales Layer authorization screen to open.
Select the access profile if the screen asks you to choose one.
Enter your Sales Layer Catalog Token.
Validate the token and continue.
Return to Gemini when the authorization flow is complete.

Test the connection

After the MCP Server is connected, ask Gemini a simple question to check whether the Sales Layer tools are available.

What Sales Layer tools are available?

Then test with a catalog-related prompt:

Show me a summary of my Sales Layer catalog.

If the connection is working, Gemini 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 such as:

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 review data quality for a specific Attribute Set.

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

Troubleshooting

Issue	Likely cause	What to do
There is no MCP option in Gemini	Your Gemini app or account may not support custom MCP servers.	Use Gemini CLI or another Gemini-compatible environment that supports MCP server configuration.
The browser authorization screen does not open	The Gemini environment may not support remote OAuth, or browser popups are blocked.	Allow popups and redirects. If needed, use the mcp-remote setup.
mcp-remote does not run	Node.js or npx may not be available on your computer, or local command execution may be blocked.	Install Node.js or ask your IT team to confirm whether local MCP command servers are allowed.
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 Sales Layer authorization flow again.
No Sales Layer tools are available	The MCP server was not loaded, or the authorization flow did not finish correctly.	Restart the Gemini environment, reconnect the MCP Server, and complete the authorization flow again.
Gemini can query data but cannot update it	The connection is using read-only access.	Use full access only if Gemini must perform write actions and your organization allows it.

Best practices

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

Use full access only for trusted 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.

If your Gemini environment does not support custom MCP servers, use a supported MCP client such as Claude Web, Claude Desktop, ChatGPT, Cursor, VS Code, or Microsoft Copilot Studio instead.