Documentation

MCP server guide

Connect Claude, ChatGPT, Codex, Cursor or any other MCP client to AnalyticFast and ask questions such as “which source brought the most revenue last month?” Connect with your AnalyticFast account in the browser. You do not need to create or paste an API key.

Connect an assistant

1. Copy the MCP URL from your website’s Settings → API & MCP page. On the hosted service it is:

https://app.analyticfast.com/mcp

1. Add it to your assistant as a remote HTTP / Streamable HTTP MCP server.
2. Select Connect or Authenticate in that app. Your browser opens AnalyticFast.
3. Sign in to AnalyticFast, review the requesting app, and choose the workspace and sites it can read. Approve the connection to return to your assistant.

The connection gives that app read-only access to your chosen analytics. You can authorize all sites in one workspace or restrict it to one site. The workspace plan must include MCP access.

Codex CLI

codex mcp add analyticfast --url https://app.analyticfast.com/mcp
codex mcp login analyticfast

Complete the browser approval, then use /mcp in Codex to check the server. See the official Codex MCP guide for other Codex surfaces.

Claude Code

claude mcp add --transport http analyticfast https://app.analyticfast.com/mcp

Inside Claude Code, run /mcp, select AnalyticFast, and follow the authentication prompt. See the official Claude Code MCP guide.

Claude, ChatGPT and other web or desktop assistants

In Claude (web, desktop or mobile), add AnalyticFast as a custom connector with the MCP URL from Settings → Connectors. In ChatGPT, add it as a custom connector from its connector settings (developer mode). Both open the AnalyticFast approval page when you connect.

Cursor, VS Code and other editors

Add a remote server entry with the MCP URL to the editor’s MCP configuration, for example:

{ "mcpServers": { "analyticfast": { "url": "https://app.analyticfast.com/mcp" } } }

The editor prompts you to authenticate the first time it uses the server.

Other MCP clients

Enter the MCP URL in the app’s remote server settings and choose its OAuth or browser sign-in option. Use a client that supports remote HTTP MCP with OAuth. Your assistant handles the credentials after browser approval.

If you previously configured AnalyticFast with a manually entered bearer token, remove that Authorization header from the client’s server settings, then reconnect using the browser flow.

Manage connections

Open Settings → API & MCP → Your connected apps to see the connections you authorized in that workspace. Disconnect immediately revokes an app’s access. To restore it, connect again from the assistant.

AnalyticFast shows the requesting app and the AnalyticFast account you are authorizing. MCP does not share your Codex or Claude account email with AnalyticFast. Complete approval in the browser window opened by the assistant you intend to connect.

Ask a question

• “Give me an overview of my store for the last 7 days.”
• “Which countries convert best?”
• “Show me the journey of the last visitor who paid.”
• “Rank traffic sources by revenue this quarter.”

Tools

Unlike the Read API, MCP tools return money in major currency units next to the currency code (18.98 with USD is $18.98), because assistants tend to misread minor units as whole dollars.

A range is optional and uses the same fields as the Read API: period, from, to, granularity and filters.

Troubleshooting

If the app asks for an API key, check that it is configured for OAuth browser sign-in and remove any old Authorization header. If sign-in expires or you disconnect the app, authenticate again from the assistant. A workspace without MCP access will ask you to change its plan.

Protocol details

The server uses Streamable HTTP at POST /mcp. It supports the 2026-07-28 protocol and earlier 2025-11-25, 2025-06-18 and 2025-03-26 clients. Requests receive JSON responses; no persistent server SSE stream is provided.

Clients can register with dynamic client registration or identify themselves with a client ID metadata document hosted at any public HTTPS URL. Browser-based clients are supported: /mcp and the OAuth endpoints answer CORS preflights and expose WWW-Authenticate without allowing credentials.

OAuth discovery, browser consent and PKCE let the client establish a connection without a shared API key. MCP requests use the issued access token; browser cookies alone never authenticate a tool call. Every tool checks the connection’s scopes, workspace and site restriction. Access also ends if the authorizing user loses workspace membership. Requests for another workspace’s sites return no data.

API tokens remain available for REST API, server events and CLI integrations.