Getting Access to Sales Layer MCP Server

Modified on Tue, 2 Jun at 10:55 AM

Before you connect an AI client to the Sales Layer MCP Server, you need a valid Sales Layer Catalog Token or API Key for the catalog you want the AI client to access.

This token identifies the Sales Layer catalog and allows the MCP Server to validate which catalog data can be queried or managed during the connection.

Note: If you need a Catalog Token, contact Sales Layer Support or your Sales Layer account representative.

Who can request access?

Access should be requested by a user who is authorized to manage integrations or external access for your Sales Layer account. This is usually an account administrator, IT owner, implementation partner, or project owner.

If you are not sure whether you are authorized to request the token, check with your internal Sales Layer administrator before contacting Support.

How to request a Catalog Token

To request a Catalog Token, contact Sales Layer Support or your Sales Layer account representative and include the information needed to identify the catalog and the connection you want to configure.

Information to include	Why it is needed
Company or account name	To identify the Sales Layer account.
Catalog or environment	To make sure the token is linked to the correct catalog.

You can contact Sales Layer Support at:

support@saleslayer.com

Remote MCP and local MCP

Sales Layer can be connected to external tools in different ways. The correct option depends on what you are building.

Option	Authentication	Typical use
Remote MCP Server	OAuth 2.0. Enter the Catalog Token in the Sales Layer authorization screen.	AI clients and tools that support remote MCP servers.
Local MCP Server	Token entered during local package or extension setup.	Local clients, controlled environments, or installations managed by IT.

Token security

Your Catalog Token gives access to catalog data, so it must be handled carefully.

Do not share the token in public channels, tickets with third parties, screenshots, or chat messages.
Do not store the token in source code or public repositories.
Use read-only access when write permissions are not required.
Disconnect MCP clients that are no longer used.
Contact Sales Layer Support if you think the token has been exposed.

Best practices

Request a Catalog Token only for the catalog and use case you need. Start with read-only access for testing, then move to full access only when your team has approved the workflow and understands which data can be modified. Keep the token secure and enter it only in the Sales Layer authorization screen for remote MCP clients.