Connect AI clients to your workspace

Zanfia exposes a hosted Model Context Protocol server. Add it to any MCP-capable AI client — Claude Code, Claude Desktop, Cursor, VS Code, Codex — and the assistant gets typed tools to read and act on your workspace: list products, write course lessons, create offers, post in your community, pull sales stats.

Connect my Zanfia workspace as an MCP server. Zanfia = platform for
selling digital products (courses, communities, pages).

Before configuring, ask me, one at a time, and wait for answers:

1. Which client? (options: "claude-ai", "chatgpt", "claude-code",
   "cursor", "vscode", "claude-desktop", "codex")
2. Only for cursor / vscode / codex / claude-desktop-json: my Zanfia
   API key? (I create it at Dashboard → Integrations → API, MCP and CLI;
   read-only scopes for analysis, write scopes only if the assistant
   should create content). claude-ai, chatgpt and claude-code use
   OAuth: no key, I sign in and approve access in the browser.

Server: type "http" (Streamable HTTP), URL https://app.zanfia.com/mcp,
header "Authorization: Bearer <API_KEY>".

claude-ai → any Claude plan (Free: one custom connector). Customize →
  Connectors → + Add → Add custom connector, URL https://app.zanfia.com/mcp,
  Continue, OAuth client "Register automatically" if asked, Add, Connect.
chatgpt → web only. Business / Enterprise / Edu: full MCP with writes
  (Business: admins and owners add it). Plus: works, writes included
  (checked on a Plus account on 22 October 2026). Free / Go: no custom
  MCP server. Plugins → + → Add custom MCP server, URL
  https://app.zanfia.com/mcp, auth OAuth, tick "I understand and want
  to continue", Create as a plugin, finish the sign-in.
No ChatGPT plan with MCP → use the AI Assistant in the Zanfia panel, or
  Claude's free plan.
claude-code → run (OAuth, browser opens on first use):
  claude mcp add zanfia --transport http https://app.zanfia.com/mcp
codex → add to ~/.codex/config.toml (and export ZANFIA_API_KEY):
  [mcp_servers.zanfia]
  url = "https://app.zanfia.com/mcp"
  bearer_token_env_var = "ZANFIA_API_KEY"
other clients → add to the MCP config JSON:
  { "mcpServers": { "zanfia": { "type": "http",
    "url": "https://app.zanfia.com/mcp",
    "headers": { "Authorization": "Bearer <API_KEY>" } } } }

Verify by calling the list-products tool. Tools follow the key's scopes:
*:read for reads, *:write for writes; insufficient-scope = the key lacks
that permission. Tool list: https://zanfia.com/help/developer-mcp/connect.md
For anything the tools don't cover, the full REST API spec is at
https://zanfia.com/openapi/workspace-api.json (docs: https://zanfia.com/llms.txt).

Authentication

Two ways in, same tools either way:

• OAuth (claude.ai, ChatGPT, Claude Code and other connector UIs) — add https://app.zanfia.com/mcp as a custom connector and the client walks you through a browser sign-in: Zanfia shows a consent screen (workspace, permissions, the app that is asking), you approve, done. No key to copy. The server implements OAuth 2.1 with PKCE, dynamic client registration and metadata discovery, so any spec-compliant MCP client connects without configuration.
• API key (Cursor, VS Code, Codex, scripts) — create a scoped API key and send it as an Authorization: Bearer header.

Tool access follows the granted scopes either way — read tools need the matching *:read scope, write tools *:write. An OAuth connection is granted every scope the app asks for (all of them by default) and shows up as a token badged Connector under Integrations → API, MCP and CLI; delete it there to disconnect the app. Connections last 90 days, then the client asks you to sign in again.

Add it to your client

Plans and menu labels below are the providers' own, as they read on 23 October 2026; only the ChatGPT Plus line comes from our own check. Both apps rename menus often: if a label differs, follow the provider's help page linked in each paragraph.

claude.ai / Claude Desktop (custom connector): every Claude plan can add one: Free (one custom connector), Pro, Max, Team and Enterprise. On Team and Enterprise an owner first adds it in Organization settings → Connectors. Claude reads and makes changes through Zanfia's tools and asks before it uses a tool; click Allow always only for tools you trust to run unsupervised. Click path: Customize → Connectors → + Add → Add custom connector (or Add → Custom → Web), enter a name, paste https://app.zanfia.com/mcp and click Continue. Keep the sign-in settings Claude detects (if it asks for an OAuth client, choose Register automatically), click Continue, then Add and Connect, and approve access on the Zanfia consent screen. Source: Claude help on custom connectors.

ChatGPT (custom MCP server, web only): full MCP, writes included, is on ChatGPT Business, Enterprise and Edu; on Business only workspace admins and owners can add the server. Plus works too, writes included: we checked it on a Plus account on 22 October 2026. Free and Go have no custom MCP server. Plan details are on OpenAI's pricing page. Click path: Plugins → + → Add custom MCP server, enter a name, paste https://app.zanfia.com/mcp under Connection, choose OAuth for authentication, tick I understand and want to continue and click Create as a plugin, then finish the sign-in. Install the plugin, start a new chat, type @ and pick it. Source: OpenAI help on custom MCP servers.

No ChatGPT plan with MCP? The simplest path is the AI Assistant in your Zanfia panel: it works on your real data, makes small safe changes right away and asks you to approve anything customers would see (how approvals work). Or connect Claude: its free plan allows one custom connector.

Claude Code (OAuth, no key):

claude mcp add zanfia --transport http https://app.zanfia.com/mcp

Claude Code opens the browser for the consent screen on first use. With an API key instead:

Claude Code (API key):

claude mcp add zanfia --transport http https://app.zanfia.com/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Cursor / VS Code / Claude Desktop (JSON MCP config):

{
  "mcpServers": {
    "zanfia": {
      "type": "http",
      "url": "https://app.zanfia.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Codex (OpenAI Codex CLI) — add to ~/.codex/config.toml (or a project-scoped .codex/config.toml), with the API key exported as an environment variable:

[mcp_servers.zanfia]
url = "https://app.zanfia.com/mcp"
bearer_token_env_var = "ZANFIA_API_KEY"

export ZANFIA_API_KEY="YOUR_API_KEY"

You can also manage the entry from the terminal with the codex mcp subcommand (codex mcp list, codex mcp add, …) instead of editing the TOML by hand.

Available tools

The server (zanfia, version 0.42.0) exposes the full Workspace API surface as 443 tools, grouped below by area. Read tools require the matching *:read scope, write tools *:write. Pages, funnels-adjacent site settings and the storefront sit under the pages scope; communities, community events, members/roles/moderation and support tickets under communities; social media under social; everything else — products, offers, courses, media, clients, orders, campaigns, emails, stats, discounts, team and the rest — under products. A key without a scope simply does not see that scope's tools in tools/list.

Destructive or irreversible tools say so in their descriptions and ask the assistant to confirm with you first — deletes, access revocation, bulk client actions, anything that sends real email (campaigns, personal client emails via send-client-email, client broadcasts, checkout-recovery emails, team invitations, system-email tests), SMS campaigns (send-sms-campaign sends real text messages billed to your own SMS provider account), bulk changes to mailing / SMS subscription (marketing consent — subscribing requires the consent reason), publishing an automation (publish-automation makes the workflow live: from then on real e-mails, text messages and webhooks fire for real customers; editing a delay or an e-mail step of an already published automation goes live right away too), deleting a client tag (delete-client-tag takes the tag off every client, and segments or automations that use it are not updated), and site-wide changes such as update-site-slug or update-site-domains. A well-behaved assistant will quote the exact target and wait for your go-ahead; several tools (e.g. merge-clients, send-email-campaign, bulk-revoke-filtered-access) additionally require a preview or count step before the write is accepted. File and video uploads are deliberately not MCP tools — binary payloads don't fit tool calls; use the CLI or API for uploads, then reference the media id from MCP. An image that is already online can be saved with import-image-from-url (the image file's own public address; JPEG, PNG, GIF, WebP or AVIF up to 20 MB; private and local network addresses are refused).

Instructions, prompts and resources

Besides tools, the server gives the client three things that let your own agent write pages without spending Zanfia AI credits:

Walkthrough for creators: Build pages with your own Claude or ChatGPT.

Community members

The same endpoint also accepts community-member API keys (created by a member of your community in the member platform under Settings → AI agents). A member key gets a separate, member-scoped tool set (server zanfia-member, 23 tools) — the MCP twin of the Community API: listing their communities and channels, reading and searching posts, comments and chat, writing posts/comments/messages as themselves (own content only), and raising and tracking their support tickets. None of the workspace tools above are available to member keys.

Member read tools: list-my-communities · list-community-channels · list-channel-posts · search-community-posts · list-post-comments · list-channel-messages · get-community-updates · get-my-notifications · list-my-support-tickets · get-support-ticket. Member write tools: create-community-post · update-community-post · delete-community-post · create-post-comment · update-post-comment · delete-post-comment · send-channel-message · edit-channel-message · delete-channel-message · mark-notifications-read · create-support-ticket · add-support-ticket-message · update-support-ticket-status.

For agents that keep an eye on a community, the get-community-updates tool (also GET /v1/communities/:communityId/updates?since=<ISO> on the Community API) returns everything new — posts, comments, and chat — across the caller's readable channels in one call: pass the returned nextSince as the next since instead of polling each channel separately. To know when someone talks to you (replies, @-mentions, reactions, DMs), member keys also get get-my-notifications and mark-notifications-read — the member's own notification inbox, shared with the platform bell.

A member can also create a read-only key (pick Read-only when generating it, or zanfia join / zanfia login --address with --read-only): it carries communities:read alone, tools/list shows only the read tools, the server instructions say the key is read-only, and a call to a write tool is refused with a message naming where a full-access key comes from.

Member requests are rate limited (per minute, per member — a 429 carries Retry-After), and content creates accept a clientRequestId UUID so retries never duplicate a post, comment, or message.

Member access is off by default: it works only in communities where the creator has enabled member API access in the community settings, and flipping the setting off immediately locks out already-issued member keys.

MCP, CLI, or raw API?

• MCP — best when a person chats with an AI client and wants it to act on the workspace directly.
• CLI — best for terminal-based agents, scripts, and CI; also the route for file and video uploads, which MCP deliberately doesn't do.
• Raw API — best for your own integrations and backends.

All three are the same underlying platform with the same permissions model, so you can mix them freely.