Incep Digital
GuidesIncep Platform owner guide
Integrations5 min read

Connecting an AI assistant

The platform can expose your store to an AI client you already use, so you can ask it to build a page, add products or adjust the design from wherever you work. This is separate from the AI built into the admin.

Connecting a client

/admin/integrations/mcp

Connections are authorised through a consent screen, the same way you would connect any third party app. You approve the connection, and you can revoke it at any time.

Note: The MCP endpoint is off by default and has to be enabled under Settings, Features. It stays off until you ask for it because it is a write surface reachable from outside the admin. Tokens created before you enable it will not work.

Browser sign in is the simpler route: add the store MCP URL to your client, and it opens the store for you to sign in and approve. A manual token exists for clients that cannot complete that flow.

Connect an AI client by browser sign in, or mint a token with a permission profile.

Scoped permissions

/admin/integrations/mcp

A connection is granted specific abilities rather than the run of the admin. Give a client the ability to draft pages without the ability to change payment settings.

Pages
Discover, create and generate pages, and apply art direction to sections.
Catalog
Read, create and edit products, images, categories, brands and variations.
Design
Read and change the design system, and preview a theme before applying it.
Settings
Store configuration, where you have granted it.

Review and audit

Every tool call a connected client makes is recorded, so there is a trail of what changed and which connection changed it. Where a change collides with someone editing in the builder, the builder wins and the AI edit is rejected rather than overwriting a person.

Note: The connector deliberately exposes no content generation and never spends your AI provider keys. The connected client is already a model: it reads your brand and writes the copy itself.