Access tokens

Create an MCP token for clients that cannot sign in, choose its tools and expiry, and revoke it.

Updated September 15, 20261 min read

For MCP clients that cannot sign in, such as scripts or self-hosted agents, use an access token. Give every client its own token, so you can revoke one without breaking the others.

Only the account Owner can create tokens.

Create a token

  1. Open Account settings, MCP and choose New token.
  2. Fill in:
    • Client name, so you recognise it later.
    • Expires: never, 30 days, 90 days or 1 year.
    • Tools this token can call: tick groups (Metrics, Players, Analysis, Growth, Revenue, Export, Knowledge) or single tools. Tools your plan does not include are marked.
  3. Choose Create token and copy it.

Tokens start with ag_mcp_.

Configure your client

Most clients take a JSON config. Replace the URL with the Server URL from Account settings, MCP and paste your token:

JSON
{
  "mcpServers": {
    "analyse": {
      "url": "<server url>",
      "headers": {
        "Authorization": "Bearer ag_mcp_..."
      }
    }
  }
}

The server speaks Streamable HTTP (POST requests, JSON responses).

Revoke a token

Tokens are listed under Connected clients with when they were last used and when they expire. Choose Revoke to stop one immediately.

Limits

  • Up to 25 tokens per account.
  • 120 calls a minute per token, and the daily call limit of your plan. See Plans and limits.