Uranium Mcp

io.github.xkelxmc由 GitHub 帳號 xkelxmc 發布v1.0.9更新於 Oct 24, 2026

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

已驗證STDIO僅桌面檔案與儲存金融

概覽

AI 產生的概覽

一個本機 MCP 伺服器，讓助理在 Uranium permaweb 入口網站上建立與瀏覽 NFT 合集和資產。

可以做什麼
列出個人、共用與外部 NFT 合集，並以名稱、代號和類型建立新的 ERC721 或 ERC1155 合集。依合集篩選、依標題搜尋、排序與分頁瀏覽資產。從本機檔案路徑或 base64 資料鑄造新 NFT 資產，可設定標題、描述、地點、版數以及是否向社群公開。上傳所列格式的圖片、影片、音訊與文件。
適用情境
當你在 portal.uranium.pro 管理 NFT 合集，並希望助理在聊天用戶端內列出、建立或鑄造合集與資產時使用。它適合批次瀏覽與以檔案為基礎的鑄造，而非一般區塊鏈操作。
執行需求
需要 Node.js 18 或更新版本，以及 Claude Desktop、Cursor、VS Code、Windsurf 或 Goose 等 MCP 用戶端。需要在 URANIUM_API_KEY 環境變數中提供 Uranium API 金鑰，該金鑰從 Uranium 帳戶設定產生。需要連線至 Uranium API 的網路；選用的 URANIUM_BASE_URL 可覆寫預設端點。
安裝前請注意
伺服器持有可對 Uranium 帳戶執行操作的 API 金鑰，請勿放入共用的設定檔。建立合集與鑄造資產會將資料寫入 permaweb，可能產生費用或無法復原，核准前請確認。鑄造的檔案會上傳至 Uranium 的 API，資產可透過 shareWithCommunity 選項設為公開可見。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Uranium Mcp，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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:

來源：README.md，提交 2fbe92f

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包，因此其工具未知。

版本歷史

1
  1. v1.0.9最新Sep 16, 2026

評分

已滿足適用檢查項的 40%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手；SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。