ClawLink

How to connect NMKR Studio to Hermes Agent

Connect NMKR Studio to Hermes with ClawLink: paste your NMKR Studio key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine.

Get started for free
Hermes Agent
Hermes Agent
ClawLink
ClawLink
NMKR Studio
NMKR Studio
NMKR StudioAPI KEYMCP

NMKR Studio provides APIs for managing NFT projects, assets, minting, sales, wallets, and related Cardano operations.. Once connected, Hermes Agent can read and act on NMKR Studio from chat — pairing, token refresh, and tool wiring handled for you.

11 tools

Most guides for giving Hermes Agent NMKR Studio access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical NMKR Studio setup: pair once in the browser and your always-on Hermes agent can act on NMKR Studio for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

Setup

It takes three steps to connect Hermes to NMKR Studio.

  1. 1

    Install and pair

    Install the ClawLink plugin, then pair Hermes with a one-time browser approval:

    hermes plugins install ClawLink-HQ/hermes-plugin --enable
  2. 2

    Connect NMKR Studio

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask Hermes Agent: "What can you do with NMKR Studio?"

Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test

Then connect NMKR Studio in the ClawLink dashboard — paste your NMKR Studio API key once.

Verify the connection by asking Hermes:

Pull the relevant data from NMKR Studio, summarize it in plain English, and point out anything that needs attention.

Using a different agent?

The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:

npx -y @useclawlink/cli login

login opens the same browser approval and stores a credential locally. Once NMKR Studio is connected in the dashboard, that agent calls the same 11 NMKR Studio tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

NMKR Studio MCP for Hermes

Looking for a NMKR Studio MCP server for Hermes Agent? ClawLink connects NMKR Studio to Hermes Agent and exposes 11 NMKR Studio tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw NMKR Studio integration works the same way.

What the Hermes Agent NMKR Studio integration can do

11 NMKR Studio tools are ready for Hermes Agent once the account is connected.

All 11 NMKR Studio tools for Hermes

ToolWhat it does
Get exchange rates nmkr_studio_get_exchange_ratesReturn NMKR's current BTC, USD, EUR, and JPY conversion rates for a supported coin; omitting
Get mint coupon balance nmkr_studio_get_mint_coupon_balanceReturn the connected account's Cardano mint-coupon balance, effective time, and documented
Get nft nmkr_studio_get_nftReturn one NFT's details using either its NMKR NFT UID or the combination of project UID and
Get project nmkr_studio_get_projectReturn details and NFT state counts for an NMKR Studio project identified by its project UID
Get project pricelist nmkr_studio_get_project_pricelistReturn the currently valid NFT prices configured for an NMKR Studio project, optionally
Get project sale conditions nmkr_studio_get_project_sale_conditionsReturn the active sale conditions configured for an NMKR Studio project
Get token metadata nmkr_studio_get_token_metadataReturn metadata for a blockchain token identified by policy ID and hex-encoded token name
List payout wallets nmkr_studio_list_payout_walletsReturn payout wallets already configured on the connected NMKR Studio account; this tool does
List project nfts nmkr_studio_list_project_nftsReturn one page of NFTs in a project filtered by lifecycle state, with a continuation cursor
List projects nmkr_studio_list_projectsReturn one page of projects owned by the connected NMKR Studio account, including identifiers
Validate nft metadata nmkr_studio_validate_nft_metadataCheck whether the metadata already stored for an NFT is valid; this read-only form does not

Try it: find the NMKR Studio tool you need

Browse the 11 NMKR Studio tools

Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.

Example prompts

Pull the relevant data from NMKR Studio, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from NMKR Studio, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from NMKR Studio, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from NMKR Studio, summarize it in plain English, and point out anything that needs attention.

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want NMKR Studio working from chat.

ManualClawLink
Credential handlingCollect, validate, store, and rotate the NMKR Studio API key yourself, then make sure every tool call uses the right account.Users complete the hosted ClawLink setup once and the connected NMKR Studio account becomes available to the agent without you building credential management.
Ongoing maintenanceYou own refresh logic, permission debugging, environment config, and every provider-specific edge case for NMKR Studio.ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usabilityYou still need to expose the right NMKR Studio actions to the runtime in a format your agent can reliably use.11 tools for NMKR Studio are already exposed through ClawLink, so the agent can read and act from chat immediately.

Composio also exposes NMKR Studio to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect NMKR Studio in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the NMKR Studio key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.

Troubleshooting

Hermes paired but still can't use NMKR Studio

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.

Connection succeeds but no tools appear

Reconnect NMKR Studio from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

"Tool schema not loaded yet" error when calling NMKR Studio tools

NMKR Studio tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every NMKR Studio call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

NMKR Studio returns 403 or "permission denied" on one action while others work

Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

API key setup works but results look incomplete

Double-check that the API key for NMKR Studio has the right scopes or account access. A valid key can still be too limited for some reads or writes.

FAQ

Is there a Hermes Agent NMKR Studio integration?

Yes. ClawLink is the fastest way to connect Hermes to NMKR Studio: link your NMKR Studio account once in the browser and Hermes Agent can call the NMKR Studio API through 11 ready-made tools — no custom code or token handling.

How do I connect NMKR Studio to Hermes with ClawLink?

Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect NMKR Studio in the dashboard and Hermes can use it from the next message — no config files, and the NMKR Studio key you paste is stored server-side instead of in your environment.

How long does it take to connect NMKR Studio to Hermes Agent?

About two minutes. Sign in, click Connect next to NMKR Studio in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

Why use ClawLink instead of wiring NMKR Studio up myself?

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want NMKR Studio working from chat.

Hermes paired but still can't use NMKR Studio

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.