Assistants (MCP)

MCP (Model Context Protocol) is the standard way an AI assistant connects to a tool and actually uses it. Bernuvia exposes its marketplace over MCP, so your assistant does not explain how to publish a template: it publishes it, in your account and with the permissions you gave it.

• You are in charge: each credential carries the permissions you set, and nothing else.
• No coding needed: it connects by pasting one line into your client.
• Works with Claude, Cursor, ChatGPT, VS Code and any client that speaks MCP.

1. 1Go to MCP in your dashboard and press Create token.
2. 2Give it a name you will recognise, for example «Claude on my laptop».
3. 3Choose the permissions: read only, buyer or seller. If you have two factor on, it will ask for your code.
4. 4Copy the token right then: for security it is never shown again. If you lose it, revoke it and create another.

Every client is configured its own way, but it always comes down to the same thing: the server address and your token in the Authorization header. The token is not typed into the command: it goes into an environment variable and the command names it.

read -rs BERNUVIA_TOKEN && export BERNUVIA_TOKEN
claude mcp add --transport http bernuvia https://www.bernuvia.com/api/mcp \
  --header "Authorization: Bearer ${BERNUVIA_TOKEN}"

$BERNUVIA_TOKEN = Read-Host "Bernuvia token"
claude mcp add --transport http bernuvia https://www.bernuvia.com/api/mcp --header "Authorization: Bearer ${BERNUVIA_TOKEN}"

{
  "mcpServers": {
    "bernuvia": {
      "url": "https://www.bernuvia.com/api/mcp",
      "headers": { "Authorization": "Bearer ${BERNUVIA_TOKEN}" }
    }
  }
}

You can hold several connections at once without them stepping on each other: one for selling, one for buying, or one per account of yours. All you have to watch is that each one has its own name and its own variable.

• One name per purpose, on the credential and on the server inside your client: bernuvia-ventas and bernuvia-compras tell themselves apart at a glance, and revoking one does not leave you without the other.
• One environment variable per credential: BERNUVIA_TOKEN_VENTAS and BERNUVIA_TOKEN_COMPRAS. That way you never paste the wrong key.
• Scope it to a folder or a project when your client allows it: the configuration lives with the project and only loads when you work there. If your client only has global configuration, different names are enough.
• Each credential carries its own permissions: a buying one cannot sell, and a selling one does not govern your agents. Your assistant only sees the functions its credential allows.

The server publishes its functions in three groups, and each one asks for its permission. You do not have to learn them: your assistant discovers them on its own when it connects, and if you want to see them one by one they are in the function reference.

• Reading: your profile and balance, the catalog, reviews, your purchases, your notifications and the help center. For example search_templates or my_purchases.
• Buying: cart, favourites, reviews, quoting with the exact breakdown, preparing the payment, closing a purchase you have not paid yet and following a dispute of yours. quote_purchase returns an identifier for that quote, and preparing the payment hands it over: if today's total is not the one you declared, the purchase is rejected instead of being created for a different amount. cancel_order closes an order of yours that has no deposit yet.
• Selling: your sales and stats, drafts, uploading the package, checking it before you submit it, sending to review, updating an already published template with update_published_template (it stays on sale while the change is reviewed), discount codes and replying to reviews. For example check_before_submit or my_sales.

This is not a promise of good behaviour: the server simply has no functions for it, so neither your assistant nor a stolen token can try.

• Sign a payment with your wallet. It prepares the purchase and hands you the link; you sign, in your browser, with your wallet. A delegate pays with its own, never with yours.
• Withdraw your money. Withdrawing requires your signature and a code sent to your email.
• Touch your account. It does not change your email, it does not touch your second factor and it does not create other credentials. A credential never mints another one.
• Get into administration. Your assistant operates as you, and only as you.

Everything that moves money ends in your browser. Your assistant walks up to the edge, hands you the link and stops.

• Paying for a purchase: it hands you the link with the amount already quoted and you sign.
• Opening, withdrawing or closing an expired dispute: it prepares the link and you sign.
• Withdrawing your earnings and activating your membership: always yours, never over MCP.

If your client knows how to draw them, some answers also arrive as cards: the catalog with its images, your cart with the total, your sales drawn out. It is in beta.

• There is nothing to install or switch on: if your client knows how, they appear on their own; if not, you get the usual text.
• A card can do less than you: it does not sign, it does not publish and it does not withdraw.
• Anything written by someone else is drawn as text. If something in there asks to release a payment, neither the card nor your assistant obeys.