BernuviaBernuvia

Connect your AI assistant (MCP)

Bernuvia speaks MCP: your assistant can search, buy, publish and check your sales with the permissions you give it — and never sign a payment.

What it is and what it's for

MCP (Model Context Protocol) is the standard way an AI assistant —Claude, for example— connects to a tool and actually uses it. Bernuvia exposes its marketplace over MCP, so your assistant doesn't explain how to publish a template: it publishes it, in your account and with your permissions.

  • They're the same functions the website uses, with the same validations, the same review and the same moderation.
  • No coding needed: it connects with one line and a token that you create and revoke whenever you want.
  • It works with Claude and with any client that speaks MCP.

There's a longer explanation, with examples, on the MCP page.

Connecting it

  1. 1Go to MCP in your dashboard and hit Create token.
  2. 2Give it a name you'll recognize (“Claude on my laptop”) and choose the permissions. If your account has 2FA, it'll ask you for the code.
  3. 3Copy the token right then: for security it's never shown again. If you lose it, revoke it and create another one.
  4. 4Paste it into your client. In Claude Code: `claude mcp add --transport http bernuvia https://www.bernuvia.com/api/mcp --header "Authorization: Bearer YOUR_TOKEN"`.

You can have up to 3 active tokens at a time. Every time one is created or deleted we let you know by email and in the bell.

The permissions

Each token carries permissions and each function asks for its own. You give it only what you want it to do:

  • Read only: catalog and reviews, your purchases, favorites, balance, notifications, referrals and stats.
  • Buyer: cart, marking favorites, leaving reviews, reporting issues and preparing payments.
  • Seller: your sales and stats, drafts, submitting for review, discount codes and replying to reviews.

The seller permission can only be granted if you have a seller account with an up-to-date subscription. If your membership expires, those functions stop responding instantly even if the token is still alive.

What your assistant CANNOT do

It's not a promise: the server simply has no functions for this, so no agent —not even a stolen token— can even try.

  • Sign a payment. It can prepare the purchase and give you the link; you do the signing in your browser with your wallet.
  • Withdraw your money. Withdrawing requires your signature and a code sent to your email.
  • Touch your account. It doesn't change your email, or your 2FA, and it doesn't create other tokens.
  • Get into the admin panel. An agent operates as you, and only as you.

Agent accounts (once Bernuvia enables them and you create one from *My agents*): they are separate accounts, with their own wallet, that never touch yours. There the agent does sign for itself —with ITS wallet and paying ITS own gas— its deposit, its seller membership and its withdrawal; Bernuvia still signs nothing for it, tops up no gas for it, and lets it into neither your account nor the admin panel.

If something goes wrong

  1. 1Go to MCP and hit Revoke on the token you're worried about: it stops working instantly.
  2. 2If you suspect your account is compromised, turn on 2FA in Security: turning it on revokes ALL your tokens at once, and closes your other sessions too.

A lost token can't pay, can't withdraw, and can't change your account: at most it does, within its permissions, what you could do yourself reading or managing your own stuff.

Related articles

Didn't solve it? Write to us from Contact or go back to the Help Center.