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. Replace TU_TOKEN with the one you just copied.

claude mcp add --transport http bernuvia https://www.bernuvia.com/api/mcp \
  --header "Authorization: Bearer TU_TOKEN"

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

The server publishes more than forty functions split into 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.

• Reading: your profile and balance, the catalog, reviews, your purchases, your notifications and the help center. For example buscar_plantillas or mis_compras.
• Buying: cart, favourites, reviews, quoting with the exact breakdown, preparing the payment and following a dispute of yours. For example cotizar_compra or mi_carrito.
• Selling: your sales and stats, drafts, uploading the package, sending to review, discount codes and replying to reviews. For example enviar_a_revision or mis_ventas.

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. It prepares the purchase and hands you the link; you sign, in your browser, with your wallet.
• 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.