# How to connect NMKR Studio to OpenClaw (paste one key, 11 tools) > Connect NMKR Studio to OpenClaw with ClawLink: paste your NMKR Studio key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/nmkr-studio The usual route to NMKR Studio access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical NMKR Studio setup: install one ClawHub skill, connect NMKR Studio in the browser, and OpenClaw can call real NMKR Studio actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to NMKR Studio. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect NMKR Studio** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect nmkr-studio # connect NMKR Studio (browser OAuth) npx -y @useclawlink/cli actions nmkr-studio # list available actions npx -y @useclawlink/cli run nmkr-studio --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect NMKR Studio in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your NMKR Studio API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from NMKR Studio, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw 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: ```bash 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## NMKR Studio MCP for OpenClaw Looking for a NMKR Studio MCP server for OpenClaw? ClawLink connects NMKR Studio to OpenClaw and exposes 11 NMKR Studio tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes NMKR Studio integration](https://claw-link.dev/hermes/nmkr-studio) works the same way. ## What the OpenClaw NMKR Studio integration can do 11 NMKR Studio tools are ready for OpenClaw once the account is connected. ### All 11 NMKR Studio tools for OpenClaw | Tool | What it does | |---|---| | **Get exchange rates** `nmkr_studio_get_exchange_rates` | Return NMKR's current BTC, USD, EUR, and JPY conversion rates for a supported coin; omitting | | **Get mint coupon balance** `nmkr_studio_get_mint_coupon_balance` | Return the connected account's Cardano mint-coupon balance, effective time, and documented | | **Get nft** `nmkr_studio_get_nft` | Return one NFT's details using either its NMKR NFT UID or the combination of project UID and | | **Get project** `nmkr_studio_get_project` | Return details and NFT state counts for an NMKR Studio project identified by its project UID | | **Get project pricelist** `nmkr_studio_get_project_pricelist` | Return the currently valid NFT prices configured for an NMKR Studio project, optionally | | **Get project sale conditions** `nmkr_studio_get_project_sale_conditions` | Return the active sale conditions configured for an NMKR Studio project | | **Get token metadata** `nmkr_studio_get_token_metadata` | Return metadata for a blockchain token identified by policy ID and hex-encoded token name | | **List payout wallets** `nmkr_studio_list_payout_wallets` | Return payout wallets already configured on the connected NMKR Studio account; this tool does | | **List project nfts** `nmkr_studio_list_project_nfts` | Return one page of NFTs in a project filtered by lifecycle state, with a continuation cursor | | **List projects** `nmkr_studio_list_projects` | Return one page of projects owned by the connected NMKR Studio account, including identifiers | | **Validate nft metadata** `nmkr_studio_validate_nft_metadata` | Check whether the metadata already stored for an NFT is valid; this read-only form does not | ## Example prompts **Get Exchange Rates** > Pull the relevant data from NMKR Studio, summarize it in plain English, and point out anything that needs attention. **Get Mint Coupon Balance** > Pull the relevant data from NMKR Studio, summarize it in plain English, and point out anything that needs attention. **Get Nft** > Pull the relevant data from NMKR Studio, summarize it in plain English, and point out anything that needs attention. **Get Project** > Pull the relevant data from NMKR Studio, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want NMKR Studio working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, 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 maintenance** | You 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 usability** | You 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. | ## ClawLink vs. Composio 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 OpenClaw 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the NMKR Studio skill but can't call the tools The ClawHub skill teaches OpenClaw about NMKR Studio, but the calls run through the ClawLink plugin and your connected account. Make sure NMKR Studio is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### 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. ### Is there a OpenClaw NMKR Studio integration? Yes. ClawLink is the fastest way to connect OpenClaw to NMKR Studio: link your NMKR Studio account once in the browser and OpenClaw can call the NMKR Studio API through 11 ready-made tools — no custom code or token handling. ### How do I add NMKR Studio to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink NMKR Studio skill from ClawHub, then you click Connect in the dashboard to authorize NMKR Studio. OpenClaw calls the tools 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 OpenClaw? About two minutes. Sign in, click Connect next to NMKR Studio in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want NMKR Studio working from chat. ### OpenClaw installed the NMKR Studio skill but can't call the tools The ClawHub skill teaches OpenClaw about NMKR Studio, but the calls run through the ClawLink plugin and your connected account. Make sure NMKR Studio is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.