> For the complete documentation index, see [llms.txt](https://help.smartico.ai/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartico.ai/welcome/technical-guides/mcp-server/mcp-who-can-use-it.md).

# MCP - Who can use it

Before a person can connect an AI assistant to the [MCP Server](https://help.smartico.ai/welcome/technical-guides/mcp-server), a few things must be in place: the feature on the label, a role on the label, an MCP access profile, and a way to sign in. This page is the checklist, and it says what to check when the MCP menu or the token screen is missing. For a TAP (The Affiliate Platform) account, see [MCP Server](https://help.theaffiliateplatform.com/apis-and-configurations/mcp-server) in the TAP help center.

## Checklist

| # | What must be in place                                                                                                                                         | Who sets it                                          | Where                                                                                                                                                                                   |
| - | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1 | The MCP feature is switched on for the label.                                                                                                                 | Smartico                                             | Ask your account manager.                                                                                                                                                               |
| 2 | The person has a back-office role on the label (not "No permissions").                                                                                        | An administrator of your label                       | **Label → BO users**                                                                                                                                                                    |
| 3 | The person has an MCP access profile other than **MCP No Access**.                                                                                            | An administrator of your label                       | **Label → BO users**, **General** tab, **MCP access profile**                                                                                                                           |
| 4 | To create tokens: the person has the role **CRM Admin** or **CRM Manager + Engineer** on every label the token covers (on TAP accounts: **Affiliate Admin**). | An administrator of your label                       | **Label → BO users**                                                                                                                                                                    |
| 5 | The person can sign in: the connection uses the address of the right environment, and the IP allowlist of the account lets the request through.               | The person, with the administrator for the allowlist | See [MCP - Connect Claude, ChatGPT, Cursor and other MCP Clients](https://help.smartico.ai/welcome/technical-guides/mcp-server/mcp-connect-claude-chatgpt-cursor-and-other-mcp-clients) |

### 1. The feature is on for the label

Smartico switches the MCP feature on for each label. Ask your account manager. When the feature is off, the MCP menu does not show for that label, and every MCP request for the label is refused with a message like "Smartico MCP is not enabled for label …". A connection that covers several labels keeps working on the labels where the feature is on.

### 2. A role on the label

MCP never gives more access than the back office. A person can use a label over MCP only when they have a role on that label. The assistant can see and change only what that person could see and change in the back office.

### 3. An MCP access profile

The access profile decides which tools a connection may use. There are five built-in profiles (**MCP Full access**, **MCP Editor**, **MCP Analyst**, **MCP Viewer**, **MCP No Access**) and custom profiles with grants per tool and per operation.

* A new back-office user starts on **MCP No Access**. An administrator must choose a profile first.
* The profile belongs to the person and applies on every label they can use.
* A service account token (created under **Label → MCP → Access tokens**) carries its own profile, chosen when the token is created.

See [MCP - Access Profiles](https://help.smartico.ai/welcome/technical-guides/mcp-server/mcp-access-profiles.md).

### 4. Permission to create tokens

Tokens are created under **Label → MCP → Access tokens**. Only the roles **CRM Admin** and **CRM Manager + Engineer** (on TAP accounts: **Affiliate Admin**) can create tokens and change MCP access profiles. The same role is needed on every label the token covers. Otherwise the save is refused with "You do not have access to label …".

A person does not need a token to use **Sign in with Smartico**, and should sign in rather than use a token. Tokens made on this screen are service account tokens: they belong to the label, and changes made with them are recorded under the label's AI/API user. Use them for scripts, Claude Code, and clients that cannot sign in.

### 5. Sign-in

* **Sign in with Smartico** opens a Smartico sign-in page. You log in with your back-office account and choose the labels the connection may use.
* The address must match your environment: `https://aichat-api<N>.smartico.ai/mcp`, where `<N>` is the number of the environment of your back office (for example `https://aichat-api2.smartico.ai/mcp`). A token from one environment is not known on another.
* If your account uses a back-office IP allowlist, it applies to MCP too. The sign-in page checks the address of your browser. Calls from ChatGPT and other web connectors come from their own servers, so their addresses must be on the allowlist. Claude's web connectors are accepted without it.

## The MCP menu is missing

Check these in order:

1. **The feature is off for this label.** Ask your account manager to switch on MCP for the label.
2. **Your role does not include the MCP screens.** The MCP menu (**Access tokens**, **Access profiles**, **Playground**, **Usage**) needs the feature to be enabled for your label and granted to your user permission group. Ask your administrator or your account manager.
3. **You are on another label.** The menu is shown per label. Switch to the label you want to use.

## The token screen is missing, or a token cannot be created

* **No Create button, or the save is refused:** your role on the label is not **CRM Admin** or **CRM Manager + Engineer**. Ask an administrator to create the token, or to change your role.
* **"You do not have access to label …":** you chose a label where you do not have one of these roles. Remove the label from the token, or ask for the role there.
* **MCP No Access is not in the profile list:** this is on purpose. A token on that profile could never connect. To stop a token, deactivate it.

## Sign-in works, but the assistant is refused

* **"Your back-office user has no access to label …":** you have no role on that label. Connect again and choose a label where you have a role.
* **A tool or operation is refused because of the profile:** the answer names the profile and what it allows. Ask your administrator for a wider profile. See [MCP - Access Profiles](https://help.smartico.ai/welcome/technical-guides/mcp-server/mcp-access-profiles.md).

More cases: [MCP - Troubleshooting](https://help.smartico.ai/welcome/technical-guides/mcp-server/mcp-troubleshooting).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.smartico.ai/welcome/technical-guides/mcp-server/mcp-who-can-use-it.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
