The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Uranium MCP listing page.
A Model Context Protocol (MCP) server for working with portal.uranium.pro - creating and managing NFT collections and assets. This server enables LLMs to interact with blockchain NFTs through a simple, structured interface.
First, install the Uranium MCP server with your client.
Standard config works in most of the tools:
Use the Claude Code CLI to add the Uranium MCP server:
Then set your URANIUM_API_KEY when prompted.
Add to your Claude Desktop configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.jsonCreate or edit the configuration file ~/.codex/config.toml and add:
For more information, see the Codex MCP documentation.
Go to Cursor Settings -> MCP -> Add new MCP Server. Name it "uranium", use command type with the command npx uranium-tools-mcp@latest. Add environment variable URANIUM_API_KEY with your API key.
Follow the MCP install guide, use the standard config above with your API key.
Go to Advanced settings -> Extensions -> Add custom extension. Name it "uranium", use type STDIO, and set the command to npx uranium-tools-mcp@latest. Add environment variable URANIUM_API_KEY with your API key. Click "Add Extension".
Go to Program in the right sidebar -> Install -> Edit mcp.json. Use the standard config above with your API key.
Follow the MCP Servers documentation. For example in ~/.config/opencode/opencode.json:
Open Qodo Gen chat panel in VSCode or IntelliJ → Connect more tools → + Add new MCP → Paste the standard config above with your API key.
Click Save.
Follow the MCP install guide, use the standard config above. You can also install the Uranium MCP server using the VS Code CLI:
After installation, the Uranium MCP server will be available for use with your GitHub Copilot agent in VS Code.
Follow Windsurf MCP documentation. Use the standard config above with your API key.
URANIUM_API_KEY (required): Your Uranium API key from portal.uranium.proURANIUM_BASE_URL (optional): API base URL. Defaults to https://gw.urnm.proIf you prefer to install locally:
Then use uranium-tools-mcp instead of npx uranium-tools-mcp@latest in the configuration.
This MCP server provides 4 main tools for NFT management:
name (string, required): Collection name (3-30 characters, letters, numbers, and [_.-] symbols) [min length: 3, max length: 30]symbol (string, required): Collection symbol (3-30 characters, letters, numbers, and underscores) [min length: 3, max length: 30]type (string, enum: ERC721, ERC1155, required): Collection type: ERC721 (single NFTs) or ERC1155 (multi-token)contractId (string, optional): Filter assets by collection IDpage (number, optional): Page number (default: 1) [min: 1, default: 1]pageSize (number, optional): Number of assets per page (default: 20, max: 100) [min: 1, max: 100, default: 20]sortBy (string, optional): Sort field (default: createdAt) [default: "createdAt"]order (string, enum: asc, desc, optional): Sort order (default: asc) [default: "asc"]quickFilter (string, optional): Search text to filter assets by titlefilePath (string, optional): Absolute path to the media file (for local files)fileData (string, optional): Base64 encoded file data (for Claude Desktop)fileName (string, optional): Original filename (required when using fileData)mimeType (string, optional): MIME type of the file (required when using fileData, e.g., 'image/png')contractId (string, required): ID of the collection to mint the asset intitle (string, required): Asset title (3-120 characters) [min length: 3, max length: 120]description (string, optional): Asset description (optional, max 255 characters) [max length: 255]location (string, optional): Location where the asset was created (optional, max 100 characters) [max length: 100]editions (number, optional): Number of editions (for ERC1155 collections only, 1-1000) [min: 1, max: 1000]shareWithCommunity (boolean, optional): Make the asset discoverable by the community (optional, default: false) [default: false]Test your MCP server with the MCP Inspector:
API Key not working: Make sure your API key is valid and has the necessary permissions at portal.uranium.pro
Connection errors: Check that the URANIUM_BASE_URL is correct (defaults to https://gw.urnm.pro)
File upload issues: Ensure the file path is absolute and the file exists
Collection creation fails: Verify that collection names and symbols follow the required format (3-30 characters, alphanumeric and underscore)
todo
For issues and questions: