You run an MCP server that connects to Uranium’s NFT tooling, enabling large language models to manage and interact with NFT collections and assets through a simple, structured interface. This guide shows you how to use the Uranium MCP Server, install it locally, configure it, and troubleshoot common issues so you can mint, list, and manage NFTs efficiently.

How to use

You interact with the Uranium MCP Server through your MCP client. Set up your client to connect via the standard local MCP configuration using an offline, stdio-based setup. Once connected, you can list collections, create new collections, list assets across collections with pagination and filtering, and create new assets by uploading media or supplying base64 data. All actions authenticate with your Uranium API key and operate against your Uranium account and the portal.

How to install

# Prerequisites: ensure you have Node.js 18+ installed
node -v
npm -v

# Local installation (recommended): install the MCP tool globally
npm install -g uranium-tools-mcp

# Or install viapnpm / yarn if you prefer
pnpm add -g uranium-tools-mcp
# or
yarn global add uranium-tools-mcp

# Start using the MCP server with the provided config

Configuration

Configure the Uranium MCP Server with your API key and desired options. The standard configuration uses npx to run the MCP tool and passes your API key via an environment variable.

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

Local installation details

If you prefer to install locally, you can install the MCP tool globally and reference it directly in your configuration.

npm install -g uranium-tools-mcp

Then configure your MCP server to use the local tool, e.g. with the same env var as above.

## Environment variables

The required environment variable is URANIUM\_API\_KEY. It authenticates requests to Uranium and authorizes asset and collection operations.

## Supported file formats

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

## Development

Build and run locally to test changes during development. The project supports building, starting, and testing the MCP server in development mode.

## Troubleshooting

Common issues include API keys not working, incorrect base URL, and file upload problems. Ensure your URANIUM\_API\_KEY is valid, URANIUM\_BASE\_URL (if set) points to the correct API gateway, and the file paths you provide are absolute and accessible.

## Testing

Test MCP functionality with the provided Inspector tool and local dev commands to simulate asset and collection operations.

## Development commands

Compile in watch mode (if you are actively developing the MCP server)

npm run dev

Build for production

npm run build

Start server locally

npm start

Clean build directory

npm run clean

## Available tools

### list\_collections

List all user collections including personal, common, and external collections.

### create\_collection

Create a new NFT collection with a name, symbol, and type (ERC721 or ERC1155).

### list\_assets

List assets with optional filtering by collection, search text, and pagination.

### create\_asset

Create a new NFT asset from a local file or base64 data, in a specified collection, with title, description, and optional editions.