Analytics, revenue attribution and A/B testing for your AI agent. Works in Claude, ChatGPT and Cursor. Ask in plain words, get answers tied to real sales.
Your agent hands you one link to approve. No key to copy, nothing to install.
Claude Code opens a Humblytics page to approve access. No key to paste.
Add a custom connector with this URL, then sign in to Humblytics to approve.
Cursor signs in through Humblytics, or use a key from API & MCP in the app.
Streamable HTTP. Send Authorization: Bearer <apiKey> from API & MCP in the app. Legacy SSE is at /sse.
marketing teams track their pages, ads and sales with Humblytics
You never name a tool. Your agent calls the right ones and answers. Figures shown are example data.
Calls query_funnel and get_pages_breakdown.
Most leave on Pricing. Only 14% of visitors reach the signup form.
Calls get_ads_attribution. Meta and Google spend, matched to Stripe sales.
Broad · US on Meta: $12,480 in Stripe sales from $4,090 spend.
Calls create_split_test. Your agent shows you the plan before it goes live.
Draft ready. It goes live when you approve it.
Copy the install prompt into your agent. It starts the connection itself, so there is no key to copy.
Sign in or create an account, then approve. One approval covers every site on your account.
Ask where you lose sales or which ads pay back. All 12 marketing skills show up in your agent too.
35 read your data. 10 change something, and those are listed under Safety.
35 of the 45 tools only read, and say so to your client. Your MCP client asks before it runs a tool that changes something, unless you turn that off. A new A/B test goes live as soon as it is created, and a top-up charges your card, so the server tells your agent to confirm with you first.
Five use your live Humblytics data. Seven are strategy and copy skills. Open source on GitHub.
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.
GuideStripe 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.
GuideThree 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.
It connects your AI agent to Humblytics through the Model Context Protocol. Your agent can read your traffic, funnels, A/B tests and revenue attribution, and set up tests when you approve.
Claude, Claude Code, ChatGPT, Cursor and any client that supports MCP. Add mcp.humblytics.com/v1 as a custom connector or server URL and sign in to Humblytics to approve. Developers can also run it locally over stdio.
10 of the 45 tools change something: creating, updating or stopping A/B tests, saving or deleting funnels, adding or removing a site, and billing top-ups. It cannot edit your ad campaigns or budgets. New tests go live as soon as they are created and top-ups charge your saved card, so your agent should confirm with you first.
The get_ads_attribution tool joins ad spend from Meta or Google with sessions and revenue from Stripe or Foxy, per campaign. It returns spend, clicks, sessions, revenue, ROAS and true CPA. It needs both an ad source and a revenue source connected.
No. A data point is one tracked event on your site, like a pageview or a click. Your agent reading data does not use them.
No. On the hosted server your client sends its own key on each request. The server passes it through to the Humblytics API and stores nothing.
Yes. The install prompt creates one if you do not have one, adds your site and installs the tracking script. One connection covers every site on your account.
Paste one prompt. Approve one link. Ask what makes you money.