Skip to main content

What the Elovate MCP can and can't do

A complete overview of what an AI assistant can do through the Elovate MCP, what always needs a person in Elovate, and what is never possible.

This is the full reference of what an AI assistant, such as Claude, can do in Elovate through the MCP. In short: the assistant can read, analyse, prepare and propose. Applying a change to your webshop always takes a person in Elovate.


Overview per area

Area

The assistant can

A person in Elovate

Analysing your data

Read products, categories, attributes, attribute sets, store views, pages, blocks and blog posts. Measure field completeness, find duplicate texts, list values in use, read quality findings and data freshness.

Nothing needed: analysis is read-only.

AI Workflows

Create a workflow with its trigger, add actions (extraction, category mapping, enrichment, translation, image generation, manual), write and tune prompts, test actions on up to 5 products, follow progress and read results.

Starts the workflow. After that, its actions are locked for changes through the MCP.

Reviewing workflow results

Read every generated item, including reasoning and confidence. If you are the assigned editor: approve items, or ask for a new generation. If you are the assigned moderator: send items back to the editor or decline them. Re-run a few specific items.

The moderator approves, and that starts the sync to the webshop.

Proposals (AI queue)

Propose changes to products, categories, pages, blocks and blog posts: texts, meta data, attribute values, category assignments, attribute and option labels. Propose a new page, block or blog post. Update or withdraw its own pending proposals.

An administrator approves or declines each proposal in the AI queue.

Attributes

Propose a new attribute (dropdown, yes/no, text or long text), new options for an existing dropdown, or adding an attribute to attribute sets.

An administrator approves in the AI queue. Only then is it created in the webshop.

Product images

Give you an upload link, match uploaded images to products by file name (SKU or EAN, with _1, _2 for the order), and propose them per product.

An administrator approves. Images are added after the existing ones; existing images are never removed.

Imports

Give you an upload link (or use a public CSV or Excel link), create an import draft, map the columns, run the validation, and settle validation issues you decide on.

Reviews and applies the import in Elovate.

Configuration

Read glossaries, translation settings, prompt templates, workflow action settings and the users who can review.

Changes glossaries, translation settings and users in Elovate.


What the assistant can never do

  • Sync anything to your webshop. Every sync is started by a person in Elovate.

  • Start a workflow, or start a whole workflow again.

  • Approve as moderator, or approve a proposal in the AI queue.

  • Apply an import. It stops after validation.

  • Act on items assigned to someone else, also not for administrators.

  • Change everything at once. Every write takes an explicit list of items, never “all” or a filter.

  • Change SKU, price, stock, status or visibility through a proposal.

  • Create a new dropdown option during an import. It proposes the option instead.

  • Receive files through the chat. Import files and images always go through an Elovate upload link; files dropped into the chat never reach Elovate.

  • Remove what was approved, such as a created attribute or option. That is done by a person in Elovate.


Built-in safety rules

  • Previews and confirmation. Bigger actions return a preview first. Declining, rescheduling, re-running items and validating an import always need your explicit confirmation.

  • Your rights apply. The assistant can only do what your Elovate user is allowed to do. Write tools are enabled per user under Settings → Users.

  • The active environment. The assistant works on the connection that is active in the Elovate interface. If you switch, it switches too.

  • No overwriting newer content. A proposal for an item that changed in the meantime becomes outdated instead of overwriting it.

  • Everything is traceable. Approved proposals show “AI proposal” as the origin in the sync log.


Good to know

  • Imports created through the MCP run once and can't be scheduled.

  • Image file names decide the product: ABC123.jpg or ABC123_1.jpg is the first image of SKU ABC123, ABC123_2.jpg the second. Files that match more than one product are never linked by guessing.

  • A test is a preview: nothing is synced and the next step of a workflow chain does not start.


Related articles

  • What is the Elovate MCP server?

  • Working with the AI queue: approve, decline and revert

  • Roles and permissions with MCP

  • Troubleshooting the Elovate MCP

Did this answer your question?