Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

API Access & Agent Setup

The MCP & API Access page connects your AI coding agents to live Humblytics data. Open it from the sidebar under Data → API.

MCP server URL: https://mcp.humblytics.com/v1 Claude connector: claude.ai/connectors/humblytics-mcp REST base URL: https://app.humblytics.com/api/external/v1/

Humblytics MCP

The Humblytics MCP server is a Model Context Protocol server that gives compatible AI agents supported access to Humblytics analytics and experiment-management tools. It is a supporting workflow for teams using Humblytics to connect paid spend, conversion work, and revenue. MCP and API access are included with current Business, Scale, and Enterprise plans; existing Plus accounts retain their current access.

What it covers

Traffic & trends

Pageviews, sessions, bounce rate

Funnels

Step-by-step conversion analysis

A/B tests

Create, read, and stop experiments

Heatmaps & clicks

Friction and engagement data

Once connected, your agent can query supported data and identify test opportunities. Experiment changes still require the user to review and approve the proposed action. The connection works with Claude, Codex, and other agents that support remote MCP servers.

Claude.ai and Claude Desktop (one click)

Using Claude in the browser or the desktop app? Install Humblytics from the Claude connector directory:

Add Humblytics to Claude

Click Connect, sign in to Humblytics and approve access. The connector is then available in every chat. You can disconnect it at any time from Claude's connector settings.

Connecting via OAuth (Recommended)

The easiest way to connect is to copy the setup prompt from the API page in your dashboard and paste it into your agent. Click Setup Humblytics MCP and select your agent type (Claude Code, Codex CLI, or Generic), then copy and paste.

The prompt instructs your agent to:

  1. Call a Humblytics endpoint to start an authorization session — no credentials needed

  2. Show you a URL to open in your browser

  3. Wait while you sign in (if needed) and click Approve access

  4. Receive an API key automatically once you approve

  5. Register the MCP server with that key — using the right config format for your agent

You don't handle the key yourself at any point. Once connected, the agent uses it on every subsequent request automatically.

The authorization link expires after 5 minutes. If it times out, just paste the prompt again.

You can revoke the generated key at any time from the API page in your Humblytics dashboard.

Setting up MCP manually (Alternative)

If you'd rather supply a key yourself — for example in a CI environment or shared machine — you can create one explicitly and configure the MCP server with it directly.

1. Create an API key

Go to the API page in your dashboard and click Create account key. Give it a name (e.g. Claude Agent, CI/CD), and copy the key immediately — it is shown only once.

2. Register the MCP server with your agent

Select your agent type below and follow the one-time setup.

Claude Code

For a property-scoped connection, add:

Codex CLI

The Codex prompt configures a [mcp_servers.humblytics] block in your Codex config with the MCP URL and the same authorization headers.

Generic

For any other agent that supports remote MCP servers:

The key is only shown once, during creation. Copy it before closing. If you lose it, revoke the key and create a new one.

API keys

API access is included with current Business, Scale, and Enterprise plans. Existing Plus accounts retain their current access. The page has two key types:

Account keys

Account keys work across all your properties and are the recommended choice for MCP and agents. Create one with Create account key, give it a name (e.g., Production, Claude Agent, CI/CD), and copy it immediately — the full key is displayed once at creation and cannot be retrieved later.

Property keys

Property keys are scoped to a single property. Switch to the correct property using the site selector before creating one. These are useful when you want to isolate a key to a specific site.

Revoking keys

Click the revoke icon next to any active key. Agents using that key lose access immediately. Revocation cannot be undone, but you can always create a new key. Previously revoked keys appear in the collapsed Revoked keys section.

Marketing skills & REST API

The Skills, REST API & reference section (collapsed by default) gives you two additional ways to work with Humblytics from an agent.

Marketing skills

Install 12 Humblytics marketing skills from the open-source humblytics-marketing-skills repository. Click Add 12 skills to your agent to copy the natural-language setup prompt, then paste it into your coding agent.

Skill
Description
API

cro-optimizer

Live funnel analysis + scored A/B test hypotheses

Yes

ab-test-generator

Generate & launch no-code split tests from analytics

Yes

heatmap-analyst

Click, scroll & rage-click friction analysis

Yes

revenue-attributor

Ad spend to Stripe revenue, ROAS + reallocation

Yes

funnel-reporter

End-to-end SaaS funnel reporting

Yes

page-cro

10-point landing page conversion audit

—

email-sequences

Onboarding, nurture & re-engagement drips

—

seo-strategist

Keyword research, gaps, on-page + technical SEO

—

marketing-strategist

Funnels, GTM, positioning, growth strategy

—

copywriting

Conversion copy for pages, emails & ads

—

ad-expert

Paid ads: Meta, Google, TikTok, LinkedIn

—

content-strategist

Articles, newsletters, social, video, SEO

—

Skills chain together with natural-language prompts:

Prompt
Chain

"Find my worst-performing page and fix it"

CRO Optimizer → Page CRO → A/B Test Gen

"Weekly performance report + recommendations"

Funnel Reporter → CRO Optimizer

"Cut my worst ad & replace the landing page"

Funnel Reporter → CRO Optimizer → A/B Test Gen → Ad Expert

Browse the full directory at humblytics.com/skills.

REST API reference

The REST API Reference card shows an example curl request against /traffic/summary with an Env var / Literal toggle. Always use Env var mode for committed commands — Literal is for one-off testing only.

Click Run test call to fire a live request against your selected property and confirm the connection returns a 200 OK.

The endpoint reference is grouped by the CRO loop:

Group
Tagline

Read

Analytics, recommendations & heatmaps

Decide

Funnels & split-test results

Ship

Split-tests & variants

Onboard

Properties & connectors

Security

OAuth flow: the key is generated server-side and stored by your agent in its own MCP config. It never appears in conversation or version control — your agent handles it automatically after the one-time authorization.

Manual key setup: if you configure the key via claude mcp add or a config file, it is embedded in your agent's MCP server registration and handled automatically after that. If you call the API directly from scripts or CI, store your key in a .env file listed in .gitignore. Never commit the literal value.

Either way: never paste a key into chat, CLAUDE.md, AGENTS.md, or any committed file. Revoke keys you no longer need.

Related

PreviousAgent Onboarding API
NextExternal Analytics API

Last updated