AI Assistant (MCP)

What this is

The Model Context Protocol (MCP) lets an AI assistant such as Claude, ChatGPT, or Manus connect directly to your Hiveality website and work on it for you: build and edit pages, manage blog posts, courses, funnels, flows, contacts, and more. You connect the assistant once, and it can use Hiveality's tools on your behalf.

Each connection is scoped to a single website and gives the assistant the same set of tools no matter how you authenticate.

Your MCP URL

Find it in Website Settings → Integrations → AI Assistant (MCP):

https://your-site.hiveality.com/api/mcp

Copy that URL — you'll paste it into your assistant.

Which method does your assistant use?

There are two connection methods. Claude and ChatGPT sign you in (OAuth). Codex, Manus, and most other clients use a Website API Key as a Bearer token. Both reach the same tools, scoped to this one website.

Method 1: sign-in (Claude and ChatGPT)

Claude

1. In Claude, open connector / MCP server settings and add a custom connector.
2. Paste your MCP URL.
3. When prompted, sign in to Hiveality and approve access.

ChatGPT (desktop and web)

ChatGPT connects custom MCP servers through Developer mode, available on paid plans (Plus, Pro, Business, and Enterprise). ChatGPT supports sign-in (OAuth) only, so a Website API Key is not used here.

1. In ChatGPT, go to Settings → Apps & Connectors → Advanced settings and turn Developer mode on.
2. Go back to Settings → Apps & Connectors → Add new connector (Create).
3. Enter a name and description, then paste your MCP URL.
4. Set Authentication to OAuth, confirm you trust the connector, and click Create.
5. Complete the Hiveality sign-in to approve access.

ChatGPT turns Memory off while Developer mode is on. That is expected behaviour.

Method 2: API key (Codex, Manus, and others)

Many assistants connect with a static token instead of a sign-in flow. For those, use a Website API Key as the Bearer token:

1. In Website Settings → Integrations, generate a Website API Key (it looks like hv_ws_…). Treat it like a password.

2. In your assistant, add a custom MCP server with your MCP URL (HTTPS).

3. For authentication, choose API key / Bearer token and paste the key:

   Authorization: Bearer hv_ws_your_key_here
   

No sign-in step is required.

Manus

Add Hiveality as a custom MCP server (not a built-in connector), then set the authentication to your Website API Key.

OpenAI Codex (CLI)

Codex reads MCP servers from ~/.codex/config.toml (or a project-scoped .codex/config.toml). Add a streamable-HTTP server and point it at your key via an environment variable:

[mcp_servers.hiveality]
url = "https://your-site.hiveality.com/api/mcp"
bearer_token_env_var = "HIVEALITY_API_KEY"

Then set the variable and start Codex:

export HIVEALITY_API_KEY="hv_ws_your_key_here"
codex

The codex mcp add command is for local (stdio) servers only. For a remote URL, edit config.toml as shown above.

Sign-in vs. API key: what's the difference?

• Same tools, same data. Both methods expose the identical tool set, scoped to the one website.
• Token lifetime. Sign-in tokens expire and refresh automatically. A Website API Key stays valid until you revoke it, which makes it a better fit for always-on or automated assistants like Codex, Manus, or n8n.
• Revoking access. Disconnect the connector (sign-in) or revoke the key in Integrations at any time.

Multiple websites

A connection — and an API key — is tied to one website. If you want an assistant to work across several sites, add a separate MCP connection (and key) for each one.

Security

• Your Website API Key grants full access to that website's data. Keep it secret, never commit it to code or share it publicly.
• Rotate or revoke a key instantly from Website Settings → Integrations if it is ever exposed.
• Each key is scoped to a single website, so a leaked key can never affect your other sites.