Claude Can Now Do Your Product Content Work in Veribl

You can now connect Claude to Veribl. Give it your PDF manuals and it writes the help articles on each product page, fills in passport data, translates everything into the languages you sell in and adds spare parts. Your team reviews and publishes. This guide covers what it does, how to set it up and the prompts to use.

Most product brands have the same backlog. The manuals exist, as PDFs from the factory or the documentation team. The product pages exist, or should. In between sits weeks of copy-paste: splitting a 48-page manual into readable sections, retyping specification tables, translating it all, and then doing the same for the next product in the range.

Digital Product Passports add a second backlog. The EU's Ecodesign for Sustainable Products Regulation (ESPR) asks for disposal instructions, expected lifetime, materials and, for many products, battery data. Much of that information is already written down. It is in the same manuals.

Veribl now has an MCP server, so Claude can do this work inside your Veribl account. You talk to Claude the way you already do. Claude reads the manuals and puts the content where it belongs.

What is MCP, in plain language?

MCP stands for Model Context Protocol. It is an open standard that lets an AI assistant use other software on your behalf.

Without MCP, Claude can read your manual and write good text, but then you have to copy that text into your systems by hand. With MCP, Claude can also do the next step itself: look up your products, create an article, save a translation.

An MCP server is the part on the software's side. Veribl's MCP server tells Claude what it is allowed to do in Veribl ("list products", "write an article", "fill passport data") and carries out each action with the permissions you gave it. Nothing else.

If you have used Claude to draft an email, this is the same thing, except the result lands in Veribl instead of in your clipboard.

What Claude can do in Veribl

1. Turn manuals into help articles on each product page

This is the main job. Drop the PDF manuals into the chat, or point Claude at manuals you already uploaded to Veribl, and ask for the articles.

Claude matches each manual to a product, reads the whole manual and plans articles that cover all of it: one article per topic, grouped into sections such as "Getting started", "Care" and "Troubleshooting". It keeps every number, setting and warning exactly as the manual states and does not add information that isn't there. It can also crop the manual's diagrams and place each one at the right step.

When a customer scans the QR code on the product, they see setup, cleaning, troubleshooting, specifications and safety information, readable on a phone and searchable. Veribl's AI support assistant answers from the same articles.

Before anything goes live, Claude asks whether to publish straight away or save the articles as drafts. Drafts are not shown to customers. Each article also records where it came from, for example "Generated through the Claude connection by Anna Berg, from p1-manual.pdf, pages 12–13", so a reviewer can check it against the source page.

2. Fill in Digital Product Passport data

For each product, Claude can read the passport checklist: what each passport rule requires for that product, what is already done, and what is missing. It then fills in what the manual actually states:

• Disposal and recycling instructions, one step or rule each
• Expected lifetime
• Materials, where the manual lists them
• Battery passport fields, where the manual gives them

Where the manual doesn't say, Claude leaves the field empty rather than guessing. Some checklist items always need a person, and those stay with your team. Claude never publishes a passport. Your team reviews and publishes it in Veribl.

Claude can also read a product's published passport and its earlier versions, so you can ask what changed between versions.

3. Translate every article

Claude checks which languages you sell in (set under Settings › Languages in Veribl) and saves each article in every one of them. Customers see the version in their own language when they scan the product.

For EU brands, this is often the biggest saving. A manual that used to need a separate translation project per language becomes one more instruction in the same conversation.

4. Create and update products

Claude checks your product list for duplicates first, then creates any product that isn't in Veribl yet. Each new product gets its product page and QR code straight away. It can also update existing products, for example the description, warranty length or materials.

It can add spare parts, accessories and consumables with the part numbers the manual gives, the tools needed to replace a part, whether the owner can replace it themselves, and how long it stays available if the manual says. Spare parts also show on the product's passport, which matters under the EU right to repair rules.

If you want customers to be able to download the original PDF as well, Claude can upload it and attach it to the product. The articles are what most customers read; the PDF is there for anyone who wants it.

5. Do the whole catalogue in one conversation

None of this has to happen one product at a time. Hand Claude the manuals for a full range and it works through them product by product: create or match the product, write the articles, translate them, fill the passport fields, add the parts. You check the drafts at the end.

Before and after

The work that remains is the work that should stay with people: checking, approving and publishing.

How to connect Claude to Veribl, step by step

Setup takes a few minutes. You need a Veribl account on the Growth or Enterprise plan.

In claude.ai or Claude Desktop:

1. Open Settings › Connectors in Claude.
2. Click Add custom connector.
3. Enter the Veribl MCP server address: https://app.veribl.com/api/mcp
4. Sign in to Veribl when Claude asks.
5. Choose what Claude may do. Products, passports and articles are on by default. Your customers' contacts and registrations stay off.
6. Click Allow. The connection appears in Veribl under Settings › API keys as "Claude (connected app)".
7. Start a new chat, drop in a manual and ask for the articles.

In Claude Code:

1. In Veribl, create an API key under Settings › API keys with Products, Passports and Articles set to Read and write.
2. Add the server:

claude mcp add --transport http veribl https://app.veribl.com/api/mcp \
  --header "Authorization: Bearer vdpp_your_key_here"

3. Ask Claude Code to work on your manuals the same way.

To disconnect, revoke the key in Settings › API keys. Every change Claude makes is in the audit log, and every call is listed under Settings › API keys › API activity. The full setup guide is at support.veribl.com/connect-claude.

Prompt library: copy, paste, adjust

These prompts work in claude.ai, Claude Desktop and Claude Code once Veribl is connected. Replace the product names with yours.

Manuals to articles for a range

Here are the manuals for our 12 air purifiers. Write the help articles for each product from its manual. Create any product that isn't in Veribl yet. Save everything as drafts.

Manuals already in Veribl

Write the articles from the manuals in Veribl for every product that doesn't have articles yet. Group them into Getting started, Care and Troubleshooting.

Translations

Translate all articles for the AirPure 300 into every language we sell in. Keep model names, part numbers and units exactly as they are.

Passport data

For each product in the AirPure range, read the passport checklist and fill in what the manual states: disposal and recycling steps, expected lifetime and battery details. Tell me which items are still missing and need a person.

Spare parts and accessories

From the parts list in this manual, add the spare parts, accessories and consumables to the product, with part numbers, the tools needed and whether the owner can replace them.

A new product from scratch

Create a product called "Kettle K2" with this description and a 2-year warranty, attach this PDF manual so customers can download it, then write its articles.

Catch up after a manual revision

This is version 3 of the AirPure 300 manual. Compare it with the current articles for that product, update anything that changed and list the changes for me.

Passport history

Show me the published passport for the AirPure 300 and what changed between its last two versions.

Why this matters for ESPR and Digital Product Passports

Two EU changes are pushing product information from paper to the product page at the same time.

First, the EU is moving toward digital instructions by default. The Machinery Regulation already allows digital instructions from 2027, and the Omnibus IV proposals would extend digital-by-default manuals, delivered through a QR code, to many more product rules, with paper as the fallback. We covered this in the EU is about to let brands go digital-first on manuals. A digital manual only helps if the content is actually readable on a phone, and that is the gap Claude closes.

Second, ESPR will require Digital Product Passports for a growing list of product groups, and batteries get their own passport under the EU Battery Regulation. The ESPR 2027 compliance guide covers the timelines and required data. The EU battery passport guide explains what applies to batteries from February 2027.

A lot of the information both rules ask for already sits in your manuals: disposal steps, expected lifetime, spare parts, safety warnings, battery specifications. Connecting Claude doesn't remove the need for your team to review and sign off. It removes the retyping.

What stays with your team

Some decisions should not be delegated, and the setup reflects that:

• You choose the permissions. Customer contacts and registrations are off unless you turn them on.
• You decide what goes live. Articles can be drafts until someone approves them. Passports are only published by a person in Veribl.
• You can see everything. Each article cites its source pages, every change is in the audit log, and every call is in API activity.
• You can stop at any time. Revoke the connection and Claude no longer has access.

Claude is good at reading a long technical document carefully and writing it out in clear sections. It is not a substitute for the person who knows whether a warning is still current. The point is to give that person a finished draft to check instead of a blank page.

Getting started

1. Make sure your Veribl account is on Growth or Enterprise.
2. Add the custom connector in Claude (or the API key in Claude Code).
3. Start with one product. Drop in its manual, ask for drafts, and review them on the product page.
4. When you're happy with the result, give Claude the rest of the range.

The Connect Claude page shows what the result looks like on a product page, and the setup guide has every step for each Claude app.

Claude is a trademark of Anthropic, PBC. Veribl's MCP server works with Claude and other AI apps that support the Model Context Protocol.