MCP tokens and permissions

Create MCP tokens per site with a preset or a detailed permission table, an expiry and a one-time secret.

Site owners manage MCP access on the MCP page of the Builder (/mcp). A token is created with a label, an expiry and permissions; the secret is shown once and never stored in readable form. Permissions are a table of areas (Pages, Builder, CMS, Forms, SEO, Languages, Media, Site, Members, Integrations) by read, write and delete, plus special rights.

How it works

  • Presets: Read only, Content (read + CMS content, forms, media), Builder (+ design system, pages, components, element trees), Publish (+ publishing), Site settings (+ languages, SEO, redirects, webhooks and other settings).
  • Special rights: publishing, custom code, animations, motion, personal data, revealed submissions, submission PII, removals approved by a person.
  • Expiry 1-90 days (default 30); high-risk tokens (publish, deletes, custom code) at most 30 days; expiry cannot be extended (recreate instead).
  • Edit label and permissions later (effective at once); revoke anytime.
  • At most 20 active tokens per site.
  • The secret has the form <secret>-<id> and is returned once.

When to use it

  • Give an agency agent content-only access
  • Give your own coding agent full builder rights for a week

Limitations

  • Expiry cannot be extended
  • 20 active tokens per site

Availability

  • Works in MCP and Designer.
  • Included in every plan.
  • Limits: 20 active tokens; expiry up to 90 days (30 for high-risk).

How to use it.

  1. Open MCP in the Builder
  2. Click New token, choose a preset or permissions and expiry
  3. Copy the secret

Questions.

I lost the token secret.

Related features.

No card needed

Build it today.Pay when it goes live.

Every feature is unmetered while you build. Checkout opens the first time you publish.