Hep.gg Documentation

MCP

Connect a model or coding agent to Hep.gg over the Model Context Protocol to read the docs and act across your apps.

Read via MCP

MCP

The Hep.gg MCP is a hosted Model Context Protocol server. Connect a model or coding agent to it once with your Hep.gg account and it can read every product doc and act across your apps on your behalf, under permissions you control. It is a Prime feature and part of the AI app.

Connecting

There are two ways to authenticate:

Auth
account login
OAuthoptional
Add the server in a client that supports MCP OAuth and sign in with Hep.gg. Best for interactive use.
personal token
hepgg_mcp_...optional
Mint a token on the dashboard and send it as Authorization: Bearer hepgg_mcp_.... Best for headless or CI clients.

Access requires Hep.gg Prime and AI access. You can revoke a token or the whole connection at any time from the dashboard, and every action is recorded for you to review.

Permissions

You grant capability per app in three classes, so a connected model only ever gets what you allow:

Scope classes
read
optional
Safe reads: list and fetch your data.
write
optional
Create and edit content. Non-destructive and free.
dangerous
optional
Sensitive actions: sends, provisioning, deletes, and spending in-platform tokens. These always run as a two-step confirm.

There are also platform scopes for your account overview, documentation, key management, and Claude tooling setup. Real money is never spent through the MCP, only in-platform Hep Tokens, and only with your confirmation.

What a connected model can do

Read the docs
Pull any product doc and a per-app capability reference as resources, so it can research without you explaining anything.
Manage credentials
Mint, list, and rotate your API keys across apps.
Operate your apps
Uploads, status pages, docs, forms, snippets, profiles, SMS, email, storage, databases, and more, under the scopes you grant.
Wire up your tooling
Set up the Claude proxy, status line, logger, and secrets in your own project.

Reading the docs over MCP

Once connected, the model reads these as resources: a capability guide, a documentation index (hepgg://docs), every product doc (hepgg://docs/<app>/<slug>), and a per-app capability list (hepgg://capabilities/<app>) covering every action it can take. Point your agent at the MCP and it becomes an instant Hep.gg expert.