Skip to main content
Kiro 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 Kiro 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 Kiro — 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 Kiro at live.

​
Add the Catalog to Kiro

1

Add the server to your Kiro MCP config

Add a remote MCP server to Kiro’s MCP config — .kiro/settings/mcp.json in your workspace, or ~/.kiro/settings/mcp.json for every workspace — pointing at the environment you want. Set oauth.clientId to kiro and omit clientSecret — the Kiro IDE supports public clients only, so there is no secret to paste:
For live, use https://mcp.api.live.nevermined.app/mcp. Use the mcp.api.<env> host (not mcp.<env>): Kiro only starts OAuth when it connects to a server that challenges, and this host challenges on the first request. You don’t need redirectUri — Kiro’s default loopback callback (path /oauth/callback, on a random port) is already registered for the kiro client, and Nevermined matches it on any port.
2

Sign in

Kiro opens Nevermined’s consent page in your browser when it connects to the server — see Approve the spending cap.

​
Approve the spending cap

Kiro opens Nevermined’s consent page when it first connects to the server. 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

Once you’ve connected and approved the cap, name the connector so Kiro reaches for it rather than answering from memory.
1

Browse the catalog

Ask “list the Nevermined catalog categories through the Nevermined connector” to see what’s available.
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 Kiro 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 Kiro. The credential stops working on its next call; discovery still works.
  • Remove the connector (Kiro side). Remove the nevermined entry from the mcpServers block in your mcp.json, or set "disabled": true on it to switch it off without deleting it.
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.