Kajabi MCP server for your AI

You need a Public API Client ID and Client Secret. In Kajabi go to Settings → Public API, click Create User API Key, name it something like "MCP", pick the user and permissions, and copy both values into the connect form. The API Key and Secret under Settings → Account Details → API Credentials are Kajabi's legacy Zapier credentials and will be rejected here.

No. There is no redirect, consent screen, or re-authentication step. PopMCP exchanges the Client ID and Secret for a short-lived access token server-side over HTTPS using the OAuth2 Client Credentials flow. Because the key belongs to one Kajabi account, the MCP server is locked to that account.

A contact is anyone on your list; they become a customer when they make their first purchase. That split runs through the tool set, so people-level lookups use list_contacts and contact_details while buyer-level lookups use list_customers and customer_details. Offer access can be read either way, through list_contacts_offers or list_customers_offers.

No. Courses, products and sites are read-only here through list_courses, course_details, list_products, list_sites and site_details. The writes stay on people and commerce: creating, updating and deleting contacts, adding and removing tags, writing contact notes, granting and revoking offers, submitting forms, canceling subscriptions, and managing webhooks.

Set the connection to read-only if you only want reporting, which leaves write tools like revoke_offer_from_contact, cancel_subscription and delete_contact unavailable. If you need writes, keep full access but turn on approval-required-for-writes so each of those calls is shown to you before it runs. Reads such as list_purchases and order_details keep working either way.

Webhook-backed events fire on a purchase, a form submission, a tag added to or removed from a contact, a successful payment including subscription renewals, and a new order. Polled events cover a contact being created, a contact becoming a customer, an unsubscribe, a bounced email, a transaction such as a charge, refund or dispute, and a Kajabi Payments payout. The rest work by change detection, such as a purchase being deactivated so a member loses access to an offer, and that access returning when it is reactivated.

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Any client that supports a remote Streamable HTTP MCP server — Claude Desktop, Claude Web, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

Loading 75 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 44-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. You can switch a connection to the full catalog at any time.

A tool is something your AI calls — there are 75 here. A trigger is something PopMCP watches for you: 20 Kajabi events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Kajabi.