# MCP Server quickstart

This page shows how to connect an MCP client to the Sales Layer MCP Server and confirm that the connection works.

## Prerequisites

Before you start, make sure you have:

* A Sales Layer account with catalog access.
* A Catalog Token. See [Authentication](/mcp-server/authentication) for how to request one.
* An MCP client that supports remote MCP servers with OAuth 2.0 and PKCE.


## Choose your endpoint

The hosted server runs at `https://mcp.saleslayer.com`. The path you enter depends on the client.

| Client | Endpoint |
|  --- | --- |
| Claude Web | `https://mcp.saleslayer.com` |
| ChatGPT | `https://mcp.saleslayer.com/mcp` |
| Microsoft Copilot Studio | `https://mcp.saleslayer.com/mcp` |
| Google Gemini | `https://mcp.saleslayer.com/mcp` |
| Cursor | `https://mcp.saleslayer.com/mcp` |
| VS Code and GitHub Copilot | `https://mcp.saleslayer.com/mcp` |
| n8n | `https://mcp.saleslayer.com/mcp` |


Claude Web requires the base URL. Entering `https://mcp.saleslayer.com/mcp` in Claude Web is a known cause of connection failure.

### Pinning the access profile in the URL

Two additional endpoints fix the access profile in the URL itself, instead of selecting it during authorization:

```text
https://mcp.saleslayer.com/onlyread/mcp
https://mcp.saleslayer.com/full/mcp
```

Use `onlyread` unless the workflow needs to write. See [Access profiles and permissions](/mcp-server/permissions).

## Connect the client

The exact menu path differs per client, but the sequence is the same.

1. Add a new MCP server or custom connector in your client, using the endpoint from the table above.
2. Start the connection. The client opens the Sales Layer authorization screen in a browser.
3. Select the access profile. Choose **Read only** for a first connection.
4. Paste your Catalog Token into the Sales Layer authorization screen and validate it.
5. Confirm the detected catalog and access profile, then continue. Leave the browser window open until the redirect finishes.
6. Return to the client and check that the server shows as connected.


Do not enter the Catalog Token as a bearer token or API key in the client configuration. It is only ever entered in the Sales Layer authorization screen. See [Authentication](/mcp-server/authentication).

### Client setup guides

Step-by-step instructions with current screenshots for each client are maintained in the Support Center:

* [MCP Server setup](https://support.saleslayer.com/support/solutions/folders/206000104473)
* [Claude Web](https://support.saleslayer.com/support/solutions/articles/206000072273)
* [ChatGPT](https://support.saleslayer.com/support/solutions/folders/206000105143)
* [Microsoft Copilot Studio](https://support.saleslayer.com/support/solutions/folders/206000104476)
* [Google Gemini](https://support.saleslayer.com/support/solutions/folders/206000105215)
* [Cursor, VS Code, and GitHub Copilot](https://support.saleslayer.com/support/solutions/folders/206000105144)
* [Automation platforms](https://support.saleslayer.com/support/solutions/folders/206000105214)


If your client is not listed, contact [Sales Layer Support](https://support.saleslayer.com/) and
describe your use case, client and version, operating environment, and required access profile.
The team will assess whether a supported remote connection is available.

## Remote configuration examples

Some clients are configured with a file instead of a form.

Cursor, connecting directly to the remote server:

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

VS Code and GitHub Copilot, in `.vscode/mcp.json`:

```json
{
  "servers": {
    "sales-layer": {
      "type": "http",
      "url": "https://mcp.saleslayer.com/mcp"
    }
  }
}
```

Never commit a Catalog Token to any of these files or to a repository.

## Local installations

Sales Layer documents and supports the hosted MCP Server through remote connections. Local server
installations, command-based packages, and local connection bridges are not covered by this guide.

If your environment requires a local installation or cannot connect to the hosted endpoint
natively, contact [Sales Layer Support](https://support.saleslayer.com/). Tell us which client and
version you use, your operating environment, the use case you need to support, and whether you
require Read-only or Full access. Do not include your Catalog Token. We will review your case and
help identify an appropriate supported approach when one is available.

## Verify the connection

Ask the assistant to list what it can do. A working connection discovers the Sales Layer tools;
Read-only omits all writes, while Full access includes the complete 71-tool catalog.

Then confirm the token and catalog resolve correctly:

> Validate my Sales Layer token and tell me which catalog it points to.


This runs the `validate_token` tool. Follow it with a structural question:

> What tables are available in my catalog, and how many records does each one have?


This combines `list_custom_entities` and `get_entity_counts`, and gives you a catalog overview to work from.

If no tools appear, or authorization fails, see [Troubleshooting](/mcp-server/troubleshooting).

## Next steps

* [Tool reference](/mcp-server/tools) — everything the assistant can call.
* [Recipes](/mcp-server/recipes) — worked conversational examples.
* [Access profiles and permissions](/mcp-server/permissions) — before enabling writes.


## Related pages

* [MCP Server overview](/mcp-server)
* [Authentication](/mcp-server/authentication)
* [Troubleshooting](/mcp-server/troubleshooting)
* [Catalog REST API overview](/apis/catalog)