Uranium Mcp

Created By
xkelxmc9 months ago
MCP for Uranium NFT tools to mint, list, and manage digital assets on the permaweb.
Overview

What is Uranium MCP?

Uranium MCP is a Model Context Protocol server designed for managing NFT tools, allowing users to mint, list, and manage digital assets on the permaweb.

How to use Uranium MCP?

To use Uranium MCP, install the server using a compatible client (like VS Code or Cursor) and configure it with your Uranium API key. You can then interact with the server to manage NFT collections and assets.

Key features of Uranium MCP?

  • Fast and efficient NFT management with direct integration to the Uranium API.
  • Support for multiple NFT collections (ERC721 and ERC1155).
  • File-based asset creation, allowing uploads of images, videos, audio, and documents as NFTs.
  • Bulk operations for listing and filtering assets across collections.

Use cases of Uranium MCP?

  1. Creating and managing NFT collections for digital art.
  2. Minting audio and video NFTs for creators.
  3. Managing assets in a decentralized manner on the permaweb.

FAQ from Uranium MCP?

  • What is required to use Uranium MCP?
    You need Node.js 18 or newer and a valid Uranium API key.

  • Can I use Uranium MCP for different types of NFTs?
    Yes, it supports both ERC721 and ERC1155 NFT standards.

  • Is there a limit on the number of assets I can manage?
    No, you can manage as many assets as your collections allow.

Server Config

{
  "mcpServers": {
    "uranium": {
      "command": "npx",
      "args": [
        "uranium-tools-mcp@latest"
      ],
      "env": {
        "URANIUM_API_KEY": "your_api_key_here"
      }
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
xkelxmc
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago