Connect an AI assistant

AnalyticsTrend has an MCP server, so an AI assistant that speaks the Model Context Protocol can read your reports and, if you let it, set up goals and funnels. Ask it "which sources converted best last month?" and it reads the same numbers the dashboard shows.

It connects with a personal access token: yours, in one account, expiring within 6 months at most.

Before you start

1. An Admin allows you. On Account → Members, an Admin turns on access tokens for you. Admins can always use them.
2. Make a token. On Account → Access tokens, give it a name, such as "Laptop", and choose:
   • What it can do: "Read reports", or, for Write and Admin members, "Read reports, and create and change goals and funnels".
   • When it expires: 1 week, 1 month or 6 months.
3. Copy it. The token, starting at_pat_, is shown once. Paste it into your client now.

Every client needs the same three things:

Address	https://analyticstrend.com/mcp
Transport	Streamable HTTP
Header	Authorization: Bearer at_pat_…

Steps for each client

Claude Code

One command, with your token in place of at_pat_…:

claude mcp add --transport http analyticstrend https://analyticstrend.com/mcp --header "Authorization: Bearer at_pat_…"

Add --scope user to have it in every project rather than only the current one.

Claude Desktop

Claude Desktop's own connectors sign in with OAuth, which AnalyticsTrend does not offer yet, and its config file cannot send a header. The mcp-remote bridge, a community package run with npx, sends it for you. Open Settings → Developer → Edit Config and add:

{
  "mcpServers": {
    "analyticstrend": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://analyticstrend.com/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer at_pat_…" }
    }
  }
}

Keep Authorization:${AUTH_HEADER} without a space: on Windows a space inside an argument breaks the command. Restart Claude Desktop afterwards. It needs Node.js installed.

Cursor

In .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project:

{
  "mcpServers": {
    "analyticstrend": {
      "url": "https://analyticstrend.com/mcp",
      "headers": { "Authorization": "Bearer ${env:ANALYTICSTREND_TOKEN}" }
    }
  }
}

Set ANALYTICSTREND_TOKEN to your token in your environment, so it is never written into a file you might commit.

VS Code

In .vscode/mcp.json. VS Code asks for the token the first time and keeps it out of the file:

{
  "servers": {
    "analyticstrend": {
      "type": "http",
      "url": "https://analyticstrend.com/mcp",
      "headers": { "Authorization": "Bearer ${input:analyticstrend-token}" }
    }
  },
  "inputs": [
    { "type": "promptString", "id": "analyticstrend-token", "description": "AnalyticsTrend access token", "password": true }
  ]
}

Other clients

Any client that connects to a remote MCP server over Streamable HTTP and can send a header works with the three values above.

Not yet: chat apps whose connectors accept only OAuth cannot connect, because AnalyticsTrend does not offer OAuth yet.

What to ask

• "Which sources converted best on Newsletter signup last month?"
• "How many visitors came from Canada this week, by browser?"
• "Create a goal for /thank-you."
• "Build a funnel from Pricing viewed to Signup completed within a day."

The tools it uses, and what each answers, are in the MCP tools reference.

What it can reach

• Your reports, for every project in the token's account: the totals the dashboard shows, for any range and filters.
• Goals and funnels, created and changed, with a token that may change them and while you are a Write or Admin member. Nothing is ever deleted through MCP.
• Never: raw events, visitor identifiers, exports, members, settings or write keys. A funnel step reached by fewer than 5 visitors stays withheld, as on the screen.

Your role is checked on every call: if an Admin makes you a Read member, your token stops changing goals at once.

Where the answers go. Whatever you ask your assistant, and what AnalyticsTrend answers, goes to the AI provider behind it, under that provider's terms. That is your choice to make: the answers are totals, never anything that identifies a visitor.

Expiry and revoking

A token stops working on its expiry date, and Account → Access tokens marks it expired. Revoke one there at any time; an Admin can revoke anyone's. If an Admin turns access tokens off for you, or you leave the account, your tokens there are deleted.

Each token can make 60 calls a minute. More than that is answered with a short wait.