Zemers Developers

Connect Zemers to an AI assistant with MCP

MCP lets a trusted AI assistant work directly with your Zemers workspace. It can create and update products, advanced sales pages, blogs, communities, standalone pages, pricing, and storefront settings while respecting the same plan limits and permissions as the creator dashboard.

Before you start

Your Zemers plan must include AI Assistant through Claude or ChatGPT. Workspace owners can check this from Creator Settings → AI & MCP. If the feature is locked, upgrade the plan or ask the workspace owner.

Connect with OAuth (recommended)

1. Open Creator Settings → AI & MCP in Zemers. 2. Copy the MCP server URL shown there. The production URL is:

https://www.zemers.com/mcp

3. In ChatGPT, Claude, or another MCP-compatible client, open its Apps, Connectors, or MCP servers settings. 4. Choose the option to add a custom remote MCP server and paste the URL. 5. Your browser opens Zemers. Sign in, choose the correct workspace, review the requested permissions, and select Allow. 6. Return to the AI client. The Zemers tools are now available.

You never paste a password or secret into the AI client. OAuth access tokens are short-lived and refresh securely in the background.

Manage a connection

Open Creator Settings → AI & MCP to see:

  • every connected AI application;
  • who connected it and when;
  • the permissions it received;
  • recent MCP actions and errors.

Select Revoke to disconnect an application immediately. All of its active Zemers access and refresh tokens are revoked. To grant access again, reconnect it and approve a new permission screen.

Permissions cannot be silently expanded. A client that needs additional permissions must send you through the Zemers approval screen again.

API-key fallback

OAuth is recommended for ChatGPT, Claude, and hosted AI clients. Developer tools that only support custom Bearer headers can use a Zemers API key:

Authorization: Bearer zmk_live_...

Generate and manage keys separately from Creator Settings → API. Both the API key scopes and your plan's MCP permissions are enforced on every MCP request.

What Zemers enforces

  • tenant isolation: a connection can access only its approved creator workspace;
  • live role permissions: removing a team member or reducing their role also reduces or removes MCP access;
  • plan module permissions for MCP Read, Write, and Delete;
  • product, page, app, blog, and forum quotas;
  • product minimum pricing and account currency;
  • content validation and builder document compatibility;
  • idempotency for create operations and pricing replacement;
  • an audit log for every tool call.

Troubleshooting

The connection page says MCP is not included

The active plan does not allow MCP Read access. Ask the workspace owner to upgrade or enable a plan that includes AI Assistant through Claude or ChatGPT.

A tool is missing

The OAuth connection may not have the required scope, the current team role may not allow that action, or the plan may allow MCP Read but not Write/Delete. Reconnect to review the current permission request.

The AI client asks you to reconnect

The refresh token may have expired or the connection may have been revoked. Remove the old connection from the AI client and connect again using the same MCP server URL.

A creation request returns a quota error

MCP uses the same quota as the creator dashboard. Archive status does not free quota slots for resources where the platform counts historical creations. Upgrade the plan or remove content according to the relevant Zemers rules.