One of a kind
The first marketplace your assistant knows how to use
Bernuvia speaks MCP: the protocol Claude and other assistants use to connect to real tools. Publishing a template, reviewing your sales or replying to a review stops being something you do by hand — you ask your agent, and it does it in your account, with your permissions.
41
actions your agent can take on your behalf, one by one
0
payments it can sign: money moves only with your wallet
8
languages: your agent answers in yours
What this is, in one sentence
MCP (Model Context Protocol) is the standard way an AI assistant connects to a tool and actually uses it, instead of just talking about it. Bernuvia exposes its marketplace over MCP, so your assistant doesn't explain how to publish a template: it publishes it.
- It isn't a chatbot bolted onto the site: it's the same functions the web app uses, with the same rules.
- No coding required: you connect it with one line and a token you create and revoke whenever you want.
- Works with Claude and any client that speaks MCP.
And now you can see it, too
If your client can render them, answers stop being paragraphs: searching returns cards with their image and price, the cart shows the total, and your sales come out drawn. If it can't, it gets the same text as always and everything still works.
- It's the protocol's official extension, not something we made up: Claude, ChatGPT and VS Code render it.
- A card can't do anything you couldn't: signing is still your wallet's job, in your browser.
- What each card may call is declared one by one, and anything you can't undo asks you twice.
It's switched on from the admin panel; switching it off brings back plain text.
Publish without leaving where you work
You finish a template in your editor. Instead of opening the browser, filling in a wizard and uploading files by hand, you tell your agent: it prepares the draft, uploads the ZIP and sends it to review with the same validations as always.
Prepare the draft
Name, description, stack, price and tags. You can keep editing it on the web whenever you want: it's the same draft.
Upload the deliverable
Your agent requests a signed upload link and uploads the ZIP directly, with no middleman.
Send it to review
It goes through the same review and the same moderation as any template. Nobody skips the queue.
And afterwards: ask how it's going. Your sales, your stats, the status of each template and why one got rejected — all without opening the dashboard.
And on the other side, buying
Your assistant can search the catalog, read you the reviews, compare prices and get the purchase ready. When it's time to pay, it hands you a link: you sign, in your browser, with your wallet.
- Search templates and read their full listing
- See your purchases and download what you've already paid for
- Quote a purchase with the exact breakdown before deciding
- Prepare the payment… and stop there
NEVER
What your agent can NEVER do
This isn't a list of good intentions: it's how it's built. The server has no function for any of this, so no agent — not even a stolen token — can attempt it.
Sign a payment
Preparing the purchase, yes; signing it, no. The signature lives in your wallet, in your browser.
Withdraw your money
Withdrawing requires your signature and a code sent to your email. It doesn't exist over MCP.
Touch your account
It can't change your email or your 2FA, and it can't create other tokens. A token never mints itself a more powerful one.
Get into the admin
Zero admin surfaces. An agent operates as you, and only as you.
You decide how much you lend it
Every token carries permissions, and every function asks for its own. You can give it read-only access so it just keeps you informed, or buyer permission so it manages your cart. The seller one only shows up if you have an active seller account.
You create and revoke them in one click from your dashboard, and we email you every time one is created or deleted.
Read onlyread
Catalog, your purchases, your balance, your stats and your notifications.
Buyerbuy
Cart, favorites, reviews, reporting issues and preparing payments.
Sellerseller
Sales, drafts, submitting to review, discount codes and replying to reviews.
Connecting it takes a minute
Create your token
In the MCP section of your dashboard. Pick the permissions and copy it: it's shown only once.
Paste it into your client
One line in Claude Code and it's connected.
Just ask
"Publish this template", "how are my sales doing?", "why was this one rejected?".
The command, as is:
claude mcp add --transport http bernuvia https://www.bernuvia.com/api/mcp \
--header "Authorization: Bearer TU_TOKEN"Quick questions
Can my agent spend my money?
No. It can leave a purchase ready and hand you the link, but signing the payment happens in your browser with your wallet. The MCP server has no function that moves funds.
What if someone steals my token?
They can read and act within the permissions you granted, nothing more: they can't pay, withdraw, change your account or create another token. You revoke it from your dashboard and it stops working instantly. Turning on 2FA also revokes all your tokens at once.
Do I need to know how to code?
No. You create the token in your dashboard, paste it into your client and talk normally. Bernuvia handles the rest.
Is this for real publishing, or a toy?
For real: it uses the same functions as the web app, with the same validations, the same review and the same moderation. The only thing that changes is who does the typing.
Do other marketplaces have this?
Not that we know of. Bernuvia was built with AI-made templates at its center, and it felt natural for AI to be able to publish and buy them too.
Meet Bernuvia
Your next template, published from your editor
Create your account, activate your token and tell your assistant.