verbwire

This MCP server provides a suite of tools to interact with the Verbwire API, enabling blockchain actions such as deploying NFT contracts, minting tokens, and managing IPFS storage. It exposes a collection of data, deployment, mint, storage, update, and utility tools that can be invoked via standardized MCP tool calls. The server is designed to be used either through NPX (no local install required) or via a local Node.js setup where you run the server.js entry point, authenticated with a Verbwire API key. Typical workflows include deploying NFT contracts on a chosen chain, minting NFTs from files or metadata, and uploading assets or metadata to IPFS for on-chain reference.

Prerequisites:

• Node.js (recommended: LTS version, Node >= 14)
• npm or yarn
• A Verbwire account with an API key

Option A: NPX (no local install)

1. Ensure Node.js is installed.
2. Use NPX to run the MCP server and provide your Verbwire API key:

npx -y @verbwire/verbwire-mcp-server

3. When prompted or via environment, set VERBWIRE_API_KEY=YOUR_API_KEY_HERE

Option B: Local installation (clone repository)

1. Clone the repo and navigate into it:

git clone https://github.com/your-org/verbwire-verbwire-mcp-server.git
cd verbwire-verbwire-mcp-server

2. Install dependencies:

npm install

3. Create a .env file in the root with your API key:

VERBWIRE_API_KEY=your_api_key_here

4. Start the server:

npm start

Note: If you plan to run via NPX often, you can continue using the NPX command in Option A. The Local installation is useful for development and when you want to pin dependencies.

Tips and considerations:

• Always provide VERBWIRE_API_KEY when configuring the MCP server to ensure authenticated requests to Verbwire.
• The NPX invocation runs the server on-demand without a global install; for development or repeated runs, prefer the local install approach.
• If you encounter network or API key errors, verify that the API key is valid and has the required permissions for the actions you perform (deployments, minting, IPFS uploads).
• The server exposes a variety of tools (data, deploy, mint, storage, update, utility). Consult the tool usage examples to construct proper JSON payloads for each operation.
• When deploying contracts or minting, ensure your target chain and contract parameters are correct (e.g., chain, contractType, recipientAddress, etc.).
• For local development, keep the .env file secure and do not commit it to version control.