🔌 Connection Methods
You need a Countly auth token, created in the Token Manager on your Countly server. This is not a dashboard password and not a personal API key — create a dedicated token for your assistant. For the simplest setup, configure it for all endpoints, allow multiple uses, and set it to never expire. Full setup guide with screenshots →
Claude Desktop
Open Settings → Developer → Local MCP Servers → Edit Config, then add
countly inside mcpServers. Fully quit and reopen Claude afterwards.
{
"mcpServers": {
"countly": {
"command": "npx",
"args": ["-y", "--prefer-online", "countly-mcp-server@latest"],
"env": {
"COUNTLY_SERVER_URL": "https://your-countly-url.com",
"COUNTLY_AUTH_TOKEN": "YOUR_TOKEN"
}
}
}
}
VS Code + GitHub Copilot
From the Command Palette run MCP: Open User Configuration to open
mcp.json, then add countly inside servers:
{
"servers": {
"countly": {
"type": "stdio",
"command": "npx",
"args": ["-y", "--prefer-online", "countly-mcp-server@latest"],
"env": {
"COUNTLY_SERVER_URL": "https://your-countly-url.com",
"COUNTLY_AUTH_TOKEN": "YOUR_TOKEN"
}
}
}
}
Check it with MCP: Show Installed Servers, then ask Copilot
@countly list my apps.
Claude Code
Run this in your terminal to add Countly over stdio:
claude mcp add countly \ -e COUNTLY_SERVER_URL=https://your-countly-url.com \ -e COUNTLY_AUTH_TOKEN=YOUR_TOKEN \ -- npx -y --prefer-online countly-mcp-server@latest
Or connect to this server over HTTP instead of running your own:
claude mcp add --transport http countly https://mcp.count.ly/mcp \ --header "X-Countly-Server-Url: https://your-countly-url.com" \ --header "X-Countly-Auth-Token: YOUR_TOKEN"
Any HTTP MCP client
Credentials travel in request headers — this is the recommended way to reach a shared server, since each request carries its own token and no credentials are stored server-side:
POST https://mcp.count.ly/mcp X-Countly-Server-Url: https://your-countly-url.com X-Countly-Auth-Token: YOUR_TOKEN Content-Type: application/json
Deprecated: the same values are still accepted as
?server_url= and ?auth_token= query parameters, but tokens in URLs
leak into access logs, proxy logs and Referer headers. This server logs a
warning when it sees one, and support will be removed in a future release. Use the headers
above instead.