VE

Verbwire MCP Server: Smart Contracts, NFTs, IPFS

Deploy smart contracts, mint NFTs, and manage IPFS storage with the Verbwire MCP server for seamless blockchain operations.

Quick Install
npx -y @verbwire/verbwire-mcp-server

Overview

The Verbwire MCP Server is an implementation of a Model Context Protocol (MCP) server that wraps the Verbwire API to perform common blockchain operations programmatically. It exposes a collection of tools for deploying smart contracts, minting NFTs, uploading assets and metadata to IPFS, querying chain data, and managing contract settings — all usable from MCP-compatible clients (for example, Claude Desktop).

For developers building tooling, bots, or automation around NFTs and blockchain workflows, this server provides a ready-made bridge between an MCP consumer and Verbwire’s REST endpoints. It simplifies multi-chain NFT workflows (deploy, mint, transfer) and reliable IPFS storage while centralizing API key management and request orchestration.

Features

  • Deploy ERC-721/1155 and other NFT contract templates across multiple chains
  • Mint NFTs from local files, URLs, or raw metadata
  • Upload files, directories, and structured metadata to IPFS
  • Query NFT ownership, collections, and transaction history
  • Cross-chain token transfer and multi-chain operations
  • Contract administration: update settings, manage allowlists, configure payouts
  • Utility tools: gas estimates, chain metadata, smart contract verification
  • Over 50 prebuilt tools grouped by capability (deploy, mint, storage, update, utility)

Installation / Configuration

Prerequisites: Node.js and a Verbwire API key (create an account at https://www.verbwire.com/ and get the API key from the dashboard).

Local install and run:

git clone https://github.com/verbwire/verbwire-mcp-server.git
cd verbwire-mcp-server
npm install
# create a .env file in the project root
echo "VERBWIRE_API_KEY=your_api_key_here" > .env
npm start

Environment variable:

  • VERBWIRE_API_KEY — your Verbwire API key

Using NPX (no clone required) inside an MCP client configuration (example: Claude Desktop):

{
  "mcpServers": {
    "verbwire": {
      "command": "npx",
      "args": [
        "-y",
        "@verbwire/verbwire-mcp-server"
      ],
      "env": {
        "VERBWIRE_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

Using a locally cloned server in an MCP client:

{
  "mcpServers": {
    "verbwire": {
      "command": "node",
      "args": [
        "/path/to/verbwire-mcp-server/server.js"
      ],
      "env": {
        "VERBWIRE_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

Available Tools / Resources

The server groups tools into categories. Below is a quick reference table of categories and representative tools.

CategoryExample tools
DeploydeployContract (nft721, nft1155, custom)
MintquickMintFromFile, mintToContract, createAndMint
StorageuploadFileToIPFS, uploadDirectoryToIPFS, createMetadata
DatagetNFTsByOwner, getCollectionInfo, getTransactionDetails
UpdatetransferToken, updateMetadata, setContractAllowlist
UtilitygetChainInfo, estimateGas, verifyContract

Full tool list and signatures are available in the repository README and code. GitHub: https://github.com/verbwire/verbwire-mcp-server

Use Cases (concrete examples)

  1. Deploy a new NFT collection to Polygon Mumbai
{
  "name": "deployContract",
  "arguments": {
    "chain": "mumbai",
    "contractType": "nft721",
    "contractName": "My Collection",
    "contractSymbol": "MC",
    "recipientAddress": "0xRecipientAddressHere"
  }
}
  1. Quick mint an NFT from a local image file
{
  "name": "quickMintFromFile",
  "arguments": {
    "chain": "mumbai",
    "filePath": "/path/to/image.jpg",
    "name": "My NFT",
    "description": "A unique digital asset"
  }
}
  1. Upload artwork and metadata to IPFS (returns IPFS URIs)
{
  "name": "uploadFileToIPFS",
  "arguments": {
    "filePath": "/path/to/file.png",
    "name": "My Artwork",
    "description": "A beautiful digital artwork"
  }
}
  1. Transfer an existing token to another wallet
{
  "name": "transferToken",
  "arguments": {
    "chain": "ethereum",
    "contractAddress": "0xContract",
    "tokenId": "123",
    "to": "0xRecipient"
  }
}

Getting Started Tips

  • Keep your VERBWIRE_API_KEY secure and scoped appropriately.
  • For development, use testnets (e.g., Mumbai) to avoid spending real funds.
  • Review the tool arguments and required fields in the repository before invoking actions that change on-chain state.
  • Use storage tools to pin metadata and assets on IPFS prior to minting to ensure long-term availability.

License & Resources

  • Source code: https://github.com/verbwire/verbwire-mcp-server
  • License: MIT
  • API docs and account: https://docs.verbwire.com/ and https://www.verbwire.com/

This MCP server is intended to accelerate integration with the Verbwire API for developers building NFT, storage, and smart contract workflows while keeping operations accessible to MCP-based clients.