Affiliate intelligence inside Claude
Hi Energy AI now ships as an official connector in the Claude directory. Claude.ai and Claude Cowork can call your live affiliate data—advertisers, deals, contacts, reports, transactions—without custom MCP glue or a hand-rolled JSON config.
Install: Hi Energy on the Claude directory
Docs: MCP server documentation · Suggested prompts
Why a directory connector?
Older MCP setups asked people to paste a server URL and headers into Claude. That was easy to get wrong and painful to share with a team.
The published connector:
- Opens from the Claude directory (one productized listing)
- Runs Auth0 OAuth so you sign in as yourself
- Uses Client ID Metadata Documents (CIMD) — the modern Claude/Auth0 registration pattern (dynamic client registration is retired)
- Talks to
https://app.hienergy.ai/mcpunder the hood with the same Pundit scopes as the REST API
You get agent-native tools; Hi Energy keeps authorization identical to the app.
Connect in three steps
- Open claude.ai/directory/connectors/hi-energy
- Click Connect and finish Auth0 sign-in with your Hi Energy account
- Ask Claude about programs, deals, reports, or contacts in your account
That is the whole setup for Claude.ai and Claude Cowork. Do not paste MCP JSON for those clients.
What you can do on day one
- Search advertisers, domains, verticals, and opportunities
- Pull deals and compare promotions
- Find contacts when you are on a paid publisher plan (or admin)
- Ask for a report in plain language — Claude should call
recommend_reportfirst - Inspect transactions and clicks in scope
- Generate deeplinks and work publisher/network credential flows when your role allows
For a deeper tool map, see What the Hi Energy AI MCP server can do.
Free vs paid on the connector
Connecting works for free accounts. Contact search and unmasked emails still require paid publisher or admin access—the connector does not bypass product gates.
Bottom line
If you live in Claude for research and outreach planning, install the official Hi Energy connector, sign in once, and keep the rest of your workflow in chat. The next article covers how that path differs from Claude Code.
Frequently Asked Questions
Direct answers to common questions about this topic — optimized for search and AI answer engines.