Token Minter

An MCP server providing tools for AI agents to mint ERC-20 tokens across multiple blockchains.
  • javascript

18

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "kukapay-token-minter-mcp": {
      "command": "node",
      "args": [
        "path/to/token-minter-mcp/server/index.js"
      ],
      "env": {
        "INFURA_KEY": "YOUR_INFURA_KEY",
        "PRIVATE_KEY": "YOUR_PRIVATE_KEY"
      }
    }
  }
}

You run a Token Minter MCP server that lets AI agents deploy ERC-20 tokens, query their data, and perform transfers across multiple blockchains with ready-to-use tools and guided prompts. It centralizes token creation, balance checks, and transaction lookups behind a simple MCP interface so you can automate token management in your applications.

How to use

You interact with the Token Minter MCP using an MCP client that connects to your local or remote MCP server. The server exposes tools to deploy tokens, transfer tokens, fetch transaction details, and read token metadata and balances. Use the tools in your prompts to perform concrete actions, then query results to confirm what happened without needing to manage blockchain details directly.

How to install

Prerequisites you must have before starting:

  • Node.js v18.x or higher

  • npm (typically bundled with Node.js)

  • A valid Infura API key for EVM network access

  • An Ethereum private key for signing transactions

Step-by-step setup commands you should run in your shell:

git clone https://github.com/kukapay/token-minter-mcp.git
cd token-minter-mcp/server
npm install

# Start the MCP server (example path from the configuration):
# Replace the path with your actual location if different
node path/to/token-minter-mcp/server/index.js

# Ensure you provide required environment variables, e.g.:
# INFURA_KEY=your_infura_key
# PRIVATE_KEY=your_private_key

Configuration

Use the following configuration snippet to run the Token Minter MCP locally. It starts the server using Node.js and passes the required environment variables for Infura access and signing transactions.

{
  "mcpServers": {
    "Token-Minter-MCP": {
      "command": "node",
      "args": ["path/to/token-minter-mcp/server/index.js"],
      "env": {
        "INFURA_KEY": "your infura key",
        "PRIVATE_KEY": "your private key"
      }
    }
  }
}

Security and best practices

Protect your Ethereum private key and Infura API key. Do not expose them in client-side code or public repositories. Use environment variables or secret management to inject these values at runtime. Regularly rotate keys and use separate keys for development and production environments.

Usage examples and expected outputs

The MCP exposes a set of tools you can call from prompts. Key tools include deployToken, transferToken, getTransactionInfo, getTokenBalance, getTokenInfo, and getBalance. You can prompt your MCP client to perform actions and then query results to verify success.

Available tools and what they do

  • deployToken: Deploys a new ERC-20 token with parameters such as name, symbol, initialSupply, decimals, and chainId.

  • transferToken: Transfers a specified amount of a token to a recipient on a chosen chain.

  • getTransactionInfo: Retrieves details for a given transaction hash on a specific chain.

  • getTokenBalance: Queries the balance of a specific ERC-20 token for the current account.

  • getTokenInfo: Reads metadata for a token (name, symbol, decimals, total supply) from its contract address.

  • getBalance: Checks the native token balance of the connected account on a given chain.

Resources and addresses for token metadata

Token metadata for a token can be retrieved via a URI like token://{chainId}/{address}, which provides structured information about the token.

Prompts for deployment guidance

Use the deployTokenGuide prompt to guide token deployment with required parameters such as chainId, name, symbol, initialSupply, and decimals. This helps you craft the exact inputs you need for a smooth deployment.

Available tools

deployToken

Deploys a new ERC-20 token with details like name, symbol, initialSupply, decimals, and chainId.

transferToken

Transfers ERC-20 tokens to a recipient on a specified chain and returns the transaction hash.

getTransactionInfo

Fetches full details for a given transaction hash on a chosen chain.

getTokenBalance

Queries the balance of a specific ERC-20 token for the current account.

getTokenInfo

Retrieves token metadata such as name, symbol, decimals, and total supply by address and chain.

getBalance

Checks the native token balance for the current account on a given chain.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational