Getting started

This page explains how to connect the Synerise MCP Server. The setup takes a few minutes and does not require writing any code.

Prerequisites

Before you start, make sure you have a Synerise account with access to the workspace you want to connect, and read permissions for the product areas you want your client to access. For example, without analytics permissions, analytics tools will return an authorization error when called.

Configuration

The following example shows how to connect the Synerise MCP Server to Claude Code.

One-time setup

Add the server using the Claude Code CLI:

claude mcp add -s user --transport http synerise-ai <MCP_ENDPOINT>

Replace <MCP_ENDPOINT> with the API URL for the data center where your workspace is hosted. See Regional endpoints for the full list.

Then, in a Claude Code session, run:

/mcp

This starts the login flow and lets you select which Synerise workspace to connect.

After adding the server, restart Claude Code so the new tools load.

Troubleshooting

• Server not listed as connected - run claude mcp list and confirm synerise-ai shows as ✓ Connected.
• "Authentication required" when calling a tool - run /mcp and log in again.
• Tools not showing up - restart Claude Code.
• Token expired - run /mcp and re-authenticate.

Verifying the connection

After the server is connected, you can verify it by asking:

What Synerise workspace am I connected to?

Your client calls the account_whoami tool and returns your workspace name and the identity of the Synerise account you logged in with. If the server is not connected, your client will not be able to answer and will indicate that the tool is unavailable.

Regional endpoints

The MCP endpoint depends on the data center where your workspace is hosted:

If you are not sure which data center your workspace uses, check the URL to which you log to the Synerise application.

Permissions and data access

The Synerise MCP Server acts on your behalf using the permissions of the Synerise account you log in with. All operations are read-only: the server can retrieve, list, and calculate, but it cannot create, update, or delete any data in your workspace.

If your account does not have access to a particular resource (for example, loyalty promotions or CRM contacts), your client will receive an authorization error when it tries to retrieve that data and will inform you accordingly.

Troubleshooting

Your client says the Synerise tools are not available

The MCP server is not connected. Check the following:

• Confirm you added the server correctly and fully restarted your client after adding it.
• Run the login command again (for example, /mcp in Claude Code) to check the connection status and re-authenticate if needed.
• Open your client's MCP log or developer console to see if the connection failed.

Your client says authentication is required

Your login session has expired or was never completed. Re-run the login command (for example, /mcp in Claude Code) and log in again.

Your client receives a 403 Forbidden error

Your Synerise account does not have permission to access the requested resource. Check your account's permissions in the Synerise application and make sure you have read access to the relevant product area.

Your client is connected to the wrong workspace

The token is workspace-scoped, chosen when you log in. Log in again and select the correct workspace.

The server starts but returns no data

Confirm that the workspace you are connected to contains the data you are asking about. For example, if you ask for recommendation campaigns and none exist, the tool returns an empty result; this is expected behavior, not an error.

What's next

Once your connection is verified, you can start using the Synerise MCP Server straight away: just ask your client questions about your workspace and it will use the available tools automatically. If you want to know what tools are available and what each one does, see Available tools.