About Janus Analytics
Janus Analytics is a read-only MCP server for coding agents and other compatible clients to query Janus analytics. It provides dashboard, event, funnel, usage, and API-key data through six tools.
Key features
- 01Dashboard and traffic statistics
- 02Filtered event-log queries
- 03Monthly usage and per-key breakdowns
- 04Funnel definitions and conversion results
- 05API key details
Use cases
- 01Review traffic and top pages
- 02Check signup funnel conversion
- 03Track monthly event usage
- 04Compare event activity by API key
MCP support
The server exposes read-only Janus analytics tools to MCP clients, including dashboard, events, usage, funnels, and API-key information.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
6Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| apiKeyId | string | No | Filter stats to a specific API key (UUID). Omit to see stats across all keys. |
Details
From the project READMEJanus Analytics MCP Server
An MCP server that connects AI coding agents to your Janus analytics. Query your dashboard, events, funnels, and usage directly from Claude Code, Cursor, Windsurf, or any MCP-compatible client.
Setup
1. Get a Janus API key with Full access scope
Sign up at addjanus.ca and create an API key in Settings. Set the scope to Full access.
Keys default to Ingest scope, which can only send events — an Ingest key returns 403 on every tool in this server. Generate a key specifically for MCP rather than reusing the one on your website: a Full access key reads all your analytics and can manage keys, so it must never appear in browser code.
Upgrading from an earlier version? Existing keys were moved to
Ingestscope when scoping shipped. If your tools started returning403, create a Full access key in Settings and updateJANUS_API_KEY.
2. Add to your MCP client
Claude Code
claude mcp add janus -- npx -y @janus-analytics/mcp-server
Then set your API key:
export JANUS_API_KEY=jns_your_key_here
Claude Desktop / Cursor / Windsurf
Add to your MCP config file:
{
"mcpServers": {
"janus": {
"command": "npx",
"args": ["-y", "@janus-analytics/mcp-server"],
"env": {
"JANUS_API_KEY": "jns_your_key_here"
}
}
}
}
Config file locations:
- Claude Desktop:
~/Library/Application Support/Claude/claude_desktop_config.json(Mac) or%APPDATA%\Claude\claude_desktop_config.json(Windows) - Cursor: Settings > MCP Servers
- Windsurf:
~/.windsurf/mcp.json
Tools
All tools are read-only — the server never modifies your data.
| Tool | Description |
|---|---|
get_dashboard_stats | Event counts, unique visitors, top pages, UTM sources, countries, bounce rate, and daily trends, with bot traffic summarized separately. Optional apiKeyId filter. |
query_events | Search the event log with filters for type, tags, date range, API key, bots (exclude by default, only, include), and pagination. |
get_usage | Current month's event usage vs. tier cap, API key count, and per-key breakdown. |
list_journeys | List all funnels with step definitions, match scope, and conversion windows. |
get_journey_results | Funnel conversion data — per-step counts, conversion rates, and median time between steps. |
list_api_keys | Your API keys with names, prefixes, allowed origins, and last-used dates. |
Example prompts
Once connected, ask your AI agent things like:
- "How's my traffic looking this week?"
- "Show me the top pages from the last 7 days"
- "What's my funnel conversion rate for the signup journey?"
- "Am I close to my usage limit this month?"
- "Which API key is getting the most events?"
Configuration
| Environment variable | Required | Description |
|---|---|---|
JANUS_API_KEY | Yes | Your Janus API key (starts with jns_). Must have Full access scope |
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.