NMKR Studio
NMKR Studio provides APIs for managing NFT projects, assets, minting, sales, wallets, and related Cardano operations.
Integration
- Vendor
- NMKR Studio
- Category
- other
- Auth
- API_KEY
- Tools
- 11
- Composio slug
nmkr_studio
Tools
- Get Exchange Rates
Return NMKR's current BTC, USD, EUR, and JPY conversion rates for a supported coin; omitting coin requests the provider's ADA default.
- Get Mint Coupon Balance
Return the connected account's Cardano mint-coupon balance, effective time, and documented mint-purchase address.
- Get NFT
Return one NFT's details using either its NMKR NFT UID or the combination of project UID and NFT name.
- Get Project
Return details and NFT state counts for an NMKR Studio project identified by its project UID.
- Get Project Pricelist
Return the currently valid NFT prices configured for an NMKR Studio project, optionally including all prices exposed by NMKR.
- Get Project Sale Conditions
Return the active sale conditions configured for an NMKR Studio project.
- Get Token Metadata
Return metadata for a blockchain token identified by policy ID and hex-encoded token name.
- List Payout Wallets
Return payout wallets already configured on the connected NMKR Studio account; this tool does not add, validate, or expose wallet secrets.
- List Project NFTs
Return one page of NFTs in a project filtered by lifecycle state, with a continuation cursor for additional pages.
- List Projects
Return one page of projects owned by the connected NMKR Studio account, including identifiers needed by project and NFT tools. Results are cached by NMKR for 10 seconds.
- Validate NFT Metadata
Check whether the metadata already stored for an NFT is valid; this read-only form does not submit or update metadata.
Setup
- Create or open a Switchy Project.
- Open Integrations and connect NMKR Studio.
- Authorise through api_key. Switchy stores the connection against your org.
- Everyone in the Project can now @-mention the NMKR Studio tools in chat.
What teammates see: by default, memories from NMKR Studio are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.