# Humblytics MCP

> Hosted Model Context Protocol server for Humblytics: analytics, heatmaps, funnels, A/B tests and revenue attribution for AI agents. 45 tools; 35 read, 10 change something (A/B tests, saved funnels, sites, billing top-ups). Ad account tools are read-only.

- Endpoint: https://mcp.humblytics.com/v1 (streamable HTTP, OAuth sign-in through app.humblytics.com, or Authorization: Bearer <api key>). Legacy SSE: https://mcp.humblytics.com/sse
- Claude Code: claude mcp add --transport http humblytics https://mcp.humblytics.com/v1
- Claude.ai and ChatGPT: add a custom connector with https://mcp.humblytics.com/v1
- Docs: https://docs.humblytics.com/api/api-access-and-agents
- Skills: https://github.com/Humblytics/humblytics-marketing-skills

## Articles

- [The Agent CRO Loop: Observe, Analyze, Test, Measure](https://mcp.humblytics.com/articles/agent-cro-loop): How an AI agent runs conversion rate optimization with Humblytics MCP: real tool calls for traffic, funnels, click data, test setup and results, and the points where you approve.
- [Which Ads Make Money? Revenue Attribution Your AI Agent Can Read Over MCP](https://humblytics.com/blog/revenue-attribution-mcp): Stripe MCP has payments. Meta and Google Ads MCP have spend. Neither tells your agent which ad made a paying customer. Here is how joined revenue attribution over MCP works, field by field.
- [How to Connect Claude, ChatGPT or Cursor to Your Website Analytics (2026)](https://humblytics.com/blog/connect-ai-agent-to-website-analytics): Three ways to get your website analytics into Claude, ChatGPT or Cursor over MCP: Google's local GA4 server, a hosted GA4 connector, or analytics with its own hosted MCP server. Which route works in which client.
- [A/B Testing MCP Servers (2026): Which Ones Let Your Agent Create, Run and Call a Test](https://humblytics.com/blog/ab-testing-mcp-server): Which A/B testing tools ship an MCP server in 2026, and how far each one lets Claude, Claude Code or Cursor go: create, launch, read results, stop and ship. Checked against each vendor's own docs.