Skip to main content
OpenCode can browse the Nevermined Catalog and pay for services as it works, without you handing over an API key. You add one server, approve a single spending cap, and OpenCode does the rest. This is the per-host walkthrough; for the concept and the other assistants, see Using the Catalog from your web assistant.

​
Before you connect

1

A Nevermined account

Free, at nevermined.app. You never share an API key with OpenCode — the consent cap is the credential.
2

A funded wallet

A paid call draws on a spending cap you approve during connect — a commerce grant: a capped, revocable budget funded from your own wallet, not a key. Fund that wallet first with the asset the service settles in — see Fund your wallet. You approve the cap itself in Approve the spending cap.
Start on sandbox, where you use testnet funds and nothing costs real money, before you point OpenCode at live.

​
Add the Catalog to OpenCode

1

Add the server to your OpenCode config

Add a remote MCP server to your OpenCode config — the global ~/.config/opencode/opencode.json, or opencode.json in a project root — pointing at the environment you want. Set the OAuth client id to opencode and leave the secret out — Nevermined accepts public PKCE clients only, so there is no secret to paste:
For live, use https://mcp.live.nevermined.app/mcp. You don’t need to set a redirect URI — OpenCode’s default loopback callback (http://127.0.0.1:19876/mcp/oauth/callback) is already registered for the opencode client, and Nevermined matches it on any port.
2

Sign in

Run opencode mcp auth nevermined. OpenCode opens Nevermined’s consent page in your browser — see Approve the spending cap.

​
Approve the spending cap

OpenCode opens Nevermined’s consent page when you run opencode mcp auth. It is the one place a human is required.
1

Check who and where

The page shows the Sandbox / Live badge and who is asking. On live, the cap is real money.
2

Set the cap and validity

Set the spending cap (USDC or EURC) and how long the grant is valid for, then Grant access.
That approval is a commerce grant: it spends only from the budget you just approved, only through the Router, and you can revoke it any time. Nevermined’s routing fee comes out of the same cap, and the grant can also read your payment history and wallet balance — the cap bounds what it can spend, not what it can see.

​
Make your first paid call

Ask for something only live data can answer, and name the connector so OpenCode reaches for it rather than answering from memory.
1

Browse for free

Ask “list the Nevermined catalog categories” — a free tool call, no sign-in.
2

Ask it to buy

“Buy the service with slug <slug> through the Nevermined connector and show me the response.” The paid call draws on the cap you approved and returns the merchant’s response.
If OpenCode answers without paying, it answered from its own knowledge — name the connector and ask for live data. More on phrasing: Catalog MCP tips.

​
Disconnect

  • Revoke the budget (Nevermined side). Open Connections and disconnect OpenCode. The credential stops working on its next call; discovery still works.
  • Remove the connector (OpenCode side). Run opencode mcp logout nevermined to clear the stored tokens (OpenCode keeps them in ~/.local/share/opencode/mcp-auth.json), then remove the nevermined entry from the mcp block in your opencode.json.
To spend again — after you disconnect, or after a cap is used up — re-run the connect step and approve a new cap. A budget is never widened or extended in place.

​
Next

Using the Catalog from your web assistant

The concept and the other assistants.

Catalog MCP — full reference

Every click path, the consent details, and every refusal code.