Uranium Mcp

io.github.xkelxmcPublished by GitHub account xkelxmcv1.0.9Updated Oct 24, 2026

MCP for Uranium NFT tools to mint, list, and manage digital assets on the permaweb.

VerifiedSTDIODesktop onlyFiles & StorageFinance

Overview

AI-generated overview

A local MCP server that lets an assistant create and browse NFT collections and assets on the Uranium permaweb portal.

What you can do
List personal, common and external NFT collections, and create new ERC721 or ERC1155 collections with a name, symbol and type. Browse assets with filtering by collection, title search, sorting and pagination. Mint a new NFT asset from a local file path or base64 data, with title, description, location, edition count and an option to share it with the community. Upload images, video, audio and documents in the listed formats.
When to use it
Use it when you manage NFT collections on portal.uranium.pro and want an assistant to list, create or mint collections and assets without leaving the chat client. It suits bulk browsing and file-based minting rather than general blockchain work.
Requirements
Node.js 18 or newer and an MCP client such as Claude Desktop, Cursor, VS Code, Windsurf or Goose. A Uranium API key supplied in the URANIUM_API_KEY environment variable, generated from the Uranium account settings. Network access to the Uranium API; the optional URANIUM_BASE_URL overrides the default endpoint.
Before you install
The server holds an API key that authorizes actions on your Uranium account, so keep it out of shared configuration files. Creating collections and minting assets writes data to the permaweb and may cost money or be irreversible; review before approving. Minted files are uploaded to Uranium's API, and assets can be made publicly discoverable via the shareWithCommunity option.

Installation

In SourceWeft

  1. Open Uranium Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Uranium MCP Server

🚀 Quick Install

[Install in VS Code] [Install in VS Code Insiders] [Install in Cursor] [Install in Goose] [Install in LM Studio]

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.

Key Features

  • Fast and efficient NFT management. Direct integration with Uranium API for instant operations.
  • Multi-collection support. Manage ERC721 and ERC1155 NFT collections seamlessly.
  • File-based asset creation. Upload images, videos, audio, and documents directly as NFTs.
  • Bulk operations. List and filter assets across multiple collections with pagination.

Requirements

  • Node.js 18 or newer
  • Uranium API key from portal.uranium.pro
  • VS Code, Cursor, Windsurf, Claude Desktop, Goose or any other MCP client

Getting Started

First, install the Uranium MCP server with your client.

Standard config works in most of the tools:

json
{  "mcpServers": {    "uranium": {      "command": "npx",      "args": ["uranium-tools-mcp@latest"],      "env": {        "URANIUM_API_KEY": "your_api_key_here"      }    }  }}
Claude Code

Use the Claude Code CLI to add the Uranium MCP server:

bash
claude mcp add uranium npx uranium-tools-mcp@latest

Then set your URANIUM_API_KEY when prompted.

Claude Desktop

Add to your Claude Desktop configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json
json
{  "mcpServers": {    "uranium": {      "command": "npx",      "args": ["uranium-tools-mcp@latest"],      "env": {        "URANIUM_API_KEY": "your_api_key_here"      }    }  }}
Codex

Create or edit the configuration file ~/.codex/config.toml and add:

toml
[mcp_servers.uranium]command = "npx"args = ["uranium-tools-mcp@latest"]env = { URANIUM_API_KEY = "your_api_key_here" }

For more information, see the Codex MCP documentation.

Cursor
Click the button to install:

[Install in Cursor]

Or install manually:

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.

Gemini CLI

Follow the MCP install guide, use the standard config above with your API key.

Goose
Click the button to install:

[Install in Goose]

Or install manually:

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".

LM Studio
Click the button to install:

[Add MCP Server uranium to LM Studio]

Or install manually:

Go to Program in the right sidebar -> Install -> Edit mcp.json. Use the standard config above with your API key.

opencode

Follow the MCP Servers documentation. For example in ~/.config/opencode/opencode.json:

json
{  "$schema": "https://opencode.ai/config.json",  "mcp": {    "uranium": {      "type": "local",      "command": [        "npx",        "uranium-tools-mcp@latest"      ],      "env": {        "URANIUM_API_KEY": "your_api_key_here"      },      "enabled": true    }  }}
Qodo Gen

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.

VS Code
Click the button to install:

[Install in VS Code] [Install in VS Code Insiders]

Or install manually:

Follow the MCP install guide, use the standard config above. You can also install the Uranium MCP server using the VS Code CLI:

bash
# For VS Codecode --add-mcp '{"name":"uranium","command":"npx","args":["uranium-tools-mcp@latest"],"env":{"URANIUM_API_KEY":"your_api_key_here"}}'

After installation, the Uranium MCP server will be available for use with your GitHub Copilot agent in VS Code.

Windsurf

Follow Windsurf MCP documentation. Use the standard config above with your API key.

Configuration

Environment Variables
  • URANIUM_API_KEY (required): Your Uranium API key from portal.uranium.pro
  • URANIUM_BASE_URL (optional): API base URL. Defaults to https://gw.urnm.pro
Example Configuration
json
{  "mcpServers": {    "uranium": {      "command": "npx",      "args": ["uranium-tools-mcp@latest"],      "env": {        "URANIUM_API_KEY": "your_api_key_here"        // URANIUM_BASE_URL is optional, defaults to https://gw.urnm.pro      }    }  }}
Local Installation

If you prefer to install locally:

bash
npm install -g uranium-tools-mcp# orpnpm add -g uranium-tools-mcp# oryarn global add uranium-tools-mcp

Then use uranium-tools-mcp instead of npx uranium-tools-mcp@latest in the configuration.

Tools

This MCP server provides 4 main tools for NFT management:

Collection Management
list_collections
  • Description: List all user collections (personal, common, and external)
  • Parameters: None
create_collection
  • Description: Create a new NFT collection
  • Parameters:
    • 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)
Asset Management
list_assets
  • Description: List assets with optional filtering by collection, search, and pagination
  • Parameters:
    • contractId (string, optional): Filter assets by collection ID
    • page (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 title
create_asset
  • Description: Create a new NFT asset from a local file or base64 data
  • Parameters:
    • filePath (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 in
    • title (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]

Supported File Formats

  • Images: JPG, JPEG, PNG, GIF, WebP, SVG
  • Video: MP4, WebM, MOV, AVI
  • Audio: MP3, WAV, OGG
  • Documents: PDF, TXT

Development

Building from Source
  1. Clone the repository:
bash
git clone https://github.com/xkelxmc/uranium-mcp.gitcd uranium-mcp
  1. Install dependencies:
bash
npm install
  1. Build the project:
bash
npm run build
Development Commands
bash
# Compile in watch modenpm run dev
# Build for productionnpm run build
# Start server locallynpm start
# Clean build directorynpm run clean

Testing

Using MCP Inspector

Test your MCP server with the MCP Inspector:

bash
# For installed versionnpx @modelcontextprotocol/inspector uranium-tools-mcp
# For local developmentnpm run build:devnpx @modelcontextprotocol/inspector node build/index.js
Development Testing
bash
# Test with stdio transportnpm run dev:stdio
# Test with HTTP transportnpm run dev:http
# Inspect with HTTP transportnpm run mcp:inspect

Troubleshooting

Common Issues
  1. API Key not working: Make sure your API key is valid and has the necessary permissions at portal.uranium.pro

  2. Connection errors: Check that the URANIUM_BASE_URL is correct (defaults to https://gw.urnm.pro)

  3. File upload issues: Ensure the file path is absolute and the file exists

  4. Collection creation fails: Verify that collection names and symbols follow the required format (3-30 characters, alphanumeric and underscore)

Project Structure

src/├── api/           # Complete copy of Uranium API from Raycast├── utils/         # Utilities for validation, formatting, etc.├── models/        # Upload primitives for working with files├── tools/         # MCP tools├── server.ts      # MCP server configuration├── index.ts       # Entry point└── config.ts      # API and MCP configuration

License

todo

Support

For issues and questions:

Source: README.md at commit 2fbe92f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.9LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.