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 分

    请在仓库或注册中心条目中声明许可证。