Connect an AI assistant to Metrikia (MCP)

Goal

By the end of this guide your AI assistant reads your Metrikia campaigns, leads, deals and attribution data straight from the conversation. The connection is an authorization from your account: no key to copy, no credentials to type.

Prerequisites

• An active Metrikia account.
• An AI assistant that supports remote MCP servers: Claude (app or browser), Claude Code, Cursor, Windsurf, ChatGPT, Grok.
• Nothing else. There is no key to generate beforehand.

Step 1. Get the server address

1. Open Settings, Intelligence section, MCP Server page.
2. Copy the address shown at the top of the page with the copy button on the right.

That address is the same for every account. Your Metrikia credentials, not the address, decide which data your assistant can reach.

Step 2. Add the connector in your assistant

Claude, app or browser

1. Open Settings, then Connectors.
2. Click Add custom connector.
3. Enter a name, for example Metrikia, and paste the server address.
4. Leave the advanced OAuth fields empty, client ID and client secret. Metrikia registers your assistant automatically.
5. Confirm.

Claude Code

Add the server with the command claude mcp add --transport http metrikia https://mcp.metrikia.io/api/v1/mcp then type /mcp in a session to start the sign-in. The official Metrikia plugin does the same and also installs the skills and agents.

Cursor, Windsurf and other clients

Declare a remote MCP server with this address in your client configuration. Clients that handle remote MCP servers open the authorization page on their own at the first call.

Step 3. Authorize access

1. A Metrikia page opens in your browser.
2. Sign in if you are not already.
3. Check the destination shown on screen: that is the application you are granting access to. Only authorize if you recognize it.
4. Click Authorize.

The screen asks for two permissions: read your data, and change it (create a lead or a deal, change a status, trigger a sync). Your assistant then receives a 15 minute access that it renews automatically, without asking you again.

Expected result

Your assistant exposes 17 Metrikia tools, 13 read and 4 write. Try a question such as: Show me my top 5 campaigns by ROAS this week, or: Are there any anomalies detected on my accounts?

Common problems

My assistant sees no Metrikia tools

The connector is added but not connected. Reopen your assistant's connector list: if it reports that a sign-in is needed, run the authorization again. Some clients need a restart after the connector is added.

Authorization fails

Check that the browser that opens is signed in to the right Metrikia account. If you manage several accounts, sign out, then add the connector again from your assistant.

My assistant reads my data but refuses to create any

The write permission was not granted. Remove the connector, add it again, and accept both permissions on the authorization screen.

I was using an API key

API keys are still accepted but are no longer the recommended mode: hosted assistants such as Claude, ChatGPT or Grok cannot send a custom header and therefore cannot use one. Reconnect your clients through authorization, then revoke the key from the MCP Server page.

Remove an access

Delete the connector in your assistant to stop it being used. To permanently revoke the authorization on the Metrikia side, contact support from the application.