Connect AI tools (MCP)
Ask your AI coding tools about your site analytics in plain language.
What it is
Glyphex runs a Model Context Protocol (MCP) server, so AI coding tools like Claude Code, Cursor, Windsurf, and any MCP client can read your site analytics in plain language. Once connected, you can ask questions such as “what were my top pages last week?” and the tool answers from your live data.
Prefer to call the data yourself? The REST API exposes the same stats over plain HTTP.
Endpoint
The server uses the Streamable HTTP transport and speaks JSON-RPC 2.0.
https://glyphex.io/api/mcp
Authentication
The MCP server uses your existing Glyphex API key. Create one in Settings > Data & API > API keys, then pass it as an HTTP header:
Authorization: Bearer glx_YOUR_API_KEY
The key is bound to a single site, so the tools only ever see that site's data.
Setup: Claude Code
Run the following command, replacing the key with your own:
claude mcp add --transport http glyphex https://glyphex.io/api/mcp \ --header "Authorization: Bearer glx_YOUR_API_KEY"
Setup: Cursor
Add Glyphex to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):
{
"mcpServers": {
"glyphex": {
"url": "https://glyphex.io/api/mcp",
"headers": { "Authorization": "Bearer glx_YOUR_API_KEY" }
}
}
}Setup: other MCP clients
Any MCP client works. Point it at the same URL https://glyphex.io/api/mcp with the same Authorization header.
Available tools
| Tool | Description |
|---|---|
get_overview | Visitors, pageviews, sessions, bounce rate, and average visit duration, with change vs the previous period. |
get_timeseries | Daily visitor and pageview counts for the selected period. |
get_top_pages | Most visited pages ranked by views. |
get_referrers | Top traffic sources by referrer domain. |
get_channels | Visitor breakdown by traffic channel (direct, organic, social, referral, and more). |
get_events | Custom event counts and unique visitors. |
get_countries | Visitor breakdown by country. |
get_devices | Visitor breakdown by device type. |
get_browsers | Visitor breakdown by browser. |
get_agents_overview | AI agent traffic: totals vs the previous period, top 10 agents, and what changed. |
get_agent_recommendations | Prioritized agent findings with copy-paste fixes (robots.txt rules, llms.txt, and more). |
get_ai_visibility | Per-page AI crawl hits, fetches, AI visits and yield. |
get_operator_roi | Per AI operator: what it takes versus what it sends back, with a suggested stance. |
get_ax_score | Agent experience score: median, distribution, worst pages with failing factors, trend. |
get_actor_overview | Agents split by actor (agentic or crawler): totals, top pages and top agents. |
get_conversion_upstream | Which AI operators sit upstream of conversions, with crawl-to-visit chains. |
get_agent_identity | Agent hits per identity class (signed, ip_verified, spoofed, unsigned_automation, unknown) and per-agent identity. |
get_policy_changes | Logged robots.txt policy changes per operator with the effect 14 days before and after. |
log_policy_change | Record a policy change for an operator so its effect is measured. Needs an owner or admin account key. |
dismiss_agent_recommendation | Dismiss an agent recommendation by id. Needs an owner or admin account key. |
All tools accept an optional range (24h, 7d, 30d, 90d, or 12m; default 30d). The ranked tools also accept limit (1-100, default 10).
Rate limits
Requests are rate-limited per API key, the same as the REST API.
Need help?
Questions about the MCP integration? Use