Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Peppermint MCP Server deploy a new ERC20 token called MyToken"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Un servidor Model Context Protocol (MCP) para la API de Peppermint Tools. Proporciona acceso completo a funcionalidades blockchain incluyendo contratos inteligentes, tokens, NFTs y más.
18 herramientas MCP para operaciones blockchain
Autenticación flexible: Plain API Key (recomendada) y HMAC-SHA512
Operaciones completas: Blockchains, contratos, tokens, vaults, transacciones
Auto-configuración: Detecta vaults automáticamente
Related MCP server: Tatum MCP Server
npm install
npm run buildPEPPERMINT_API_KEY: Tu API key de Peppermint
PEPPERMINT_INSECURE_KEY: "1" para Plain API Key, "0" para HMAC
{
"mcpServers": {
"peppermint": {
"command": "node",
"args": ["/ruta/completa/al/proyecto/dist/flexible-server.js"],
"env": {
"PEPPERMINT_API_KEY": "tu-api-key",
"PEPPERMINT_INSECURE_KEY": "1"
}
}
}
}# Ejecutar servidor
npm start
# Desarrollo
npm run devget_auth_info - Ver método de autenticación actual
list_blockchains - Listar blockchains disponibles
get_blockchain - Obtener detalles de blockchain
list_contracts - Listar contratos
get_contract - Obtener contrato específico
deploy_contract - Desplegar contrato
read_contract - Leer datos de contrato
write_contract - Escribir datos a contrato
create_token - Crear token ERC20
mint_token - Mint tokens
burn_token - Burn tokens
transfer_erc20 - Transferir tokens ERC20 desde un wallet
list_vaults - Listar vaults
get_vault - Obtener vault específico
create_vault - Crear vault
list_transactions - Listar transacciones
get_transaction - Obtener transacción específica
create_wallet - Crear wallet
src/
├── flexible-server.ts # Servidor MCP principal
├── flexible-client.ts # Cliente API de Peppermint
├── flexible-auth.ts # Sistema de autenticación
└── types.ts # Definiciones de tiposISC
Burn tokens from the caller
Inputs: amount (required), contractId (required).
Create a new ERC20 token
Inputs: name (required), symbol (required), decimals (required), blockchainId (required), +2 more.
Create a new vault
Inputs: name (required), description, blockchainIds.
Create a new wallet
Inputs: blockchainId (required), vaultId.
Deploy a new smart contract
Inputs: name (required), type (required), blockchainId (required), abi, +3 more.
Get information about current authentication method
Inputs: no named parameters.
Get details of a specific blockchain
Inputs: id (required).
Get details of a specific contract
Inputs: id (required).
Get details of a specific transaction
Inputs: id (required).
Get details of a specific vault
Inputs: id (required).
List all available blockchains
Inputs: no named parameters.
List all contracts
Inputs: no named parameters.
List all transactions
Inputs: no named parameters.
List all vaults
Inputs: no named parameters.
Mint tokens to an address
Inputs: to (required), amount (required), contractId (required).
Read data from a smart contract
Inputs: contractId (required), functionName (required), params.
Transfer ERC20 tokens from a wallet to another address
Inputs: to (required), amount (required), walletId (required), tokenAddress (required).
Write data to a smart contract
Inputs: params (required), contractId (required), functionName (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 18 tools
Most tools have clear, distinct purposes (auth, blockchains, contracts, transactions, vaults, tokens). A few near-boundaries exist, e.g., create_token vs deploy_contract, but descriptions clarify the difference.
All tool names follow a consistent verb_noun snake_case pattern (get_, list_, create_, deploy_, read_, write_, mint_, burn_, transfer_). No mixed conventions or vague names.
18 tools is on the higher side but appropriate given the broad scope covering blockchains, contracts, transactions, vaults, and tokens. Each tool addresses a distinct operation, though a few could be consolidated without loss.
The surface covers core operations for auth, blockchain info, contract lifecycle (deploy/read/write), transactions, vaults, and token management. Missing native token transfers or wallet balance queries are minor gaps given the token/contract focus.
Manage blockchain RPC keys, networks, usage and prepaid billing with a scoped SolidRPC token.
57 tools: token prices, wallet and contract risk, liquidity pools, FX. 25 free calls.
Wallet balances, ERC-20, blocks, transactions, receipts, ENS and payment checks, pay per call
366 tools: balances, blocks, gas, txs and logs on 5 EVM chains, plus Bitcoin. 25 free calls.
