Token Minter MCP MCP Server

An MCP server providing tools for AI agents to mint ERC-20 tokens across multiple blockchains. The token minter mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

• Deploy new ERC-20 tokens with customizable parameters
• Query token metadata (name, symbol, decimals, total supply)
• Initiate token transfers (returns transaction hash without confirmation)
• Retrieve transaction details by hash
• Check native token balance of the current account
• Access token metadata via URI

Its toolset

Everything the assistant can do here goes through one of these:

• deployToken — Deploys a new ERC-20 token (name, symbol, initialSupply, decimals, chainId)
• transferToken — Transfers ERC-20 tokens (tokenAddress, toAddress, amount, chainId)
• getTransactionInfo — Retrieves transaction details (txHash, chainId)
• getTokenBalance — Queries the balance of a specific ERC-20 token for the current account
• getTokenInfo — Queries ERC-20 token metadata (tokenAddress, chainId)
• getBalance — Checks native token balance (chainId)
• name — The token's full name (e.g., "MyToken")
• symbol — The token's ticker (e.g., "MTK")
• initialSupply — Amount in token units (e.g., 1000000 for 1M tokens, default 1,000,000)
• decimals — Optional number of decimals (default is 18)
• chainId — Optional chain ID (default is 1 for Ethereum)
• Tools — The Tools tool exposed by this server

Adding it to your client

hardhat on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

You will need 2 environment variables: INFURA_KEY, PRIVATE_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• 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

When to reach for it

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Token Minter MCP's toolset — deployToken, transferToken, getTransactionInfo and 11 more — is a fair guide to whether it matches your workflow. It is maintained by kukapay; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Token Minter MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the token minter mcp mcp server does with a few real requests.