kaspa

Kaspa MCP Server exposes a set of MCP tools that let you interact with the Kaspa network via a WASM SDK backend. The server supports managing wallets, connecting to Kaspa networks, checking balances, sending transactions with optional payloads, estimating fees, generating mnemonics, and validating addresses. To begin, connect to a Kaspa network using kaspa_connect, then create or load a wallet with kaspa_create_wallet or kaspa_setup_preconfigured_wallet. Use kaspa_get_balance to query addresses, and kaspa_send_transaction to transfer KAS with optional payloads. For planning transactions, kaspa_estimate_fee helps approximate costs, and kaspa_generate_mnemonic or kaspa_validate_address provide utility capabilities. All operations can be scoped to a session via sessionId to support concurrent usage. Preconfigured wallet usage relies on environment variables (KASPA_WALLET_MNEMONIC and KASPA_WALLET_PRIVATE_KEY) to keep sensitive data out of logs and AI subprocesses.

Prerequisites:

• Node.js (v14+ recommended) and npm
• Access to a shell/terminal

1. Install dependencies and build the MCP server: npm run install-all npm run build

2. Run the server (example): node /path/to/kaspa-mcp-server/dist/index.js

3. Optionally run in development mode or with container orchestration as needed. If you use the provided npm scripts in your environment, ensure your environment variables (see below) are set before starting.

Environment variable guidance (for secure operation):

• KASPA_WALLET_MNEMONIC: 12-24 word mnemonic for wallet setup (if using preconfigured wallet)
• KASPA_WALLET_PRIVATE_KEY: Hex private key for wallet setup
• KASPA_DEFAULT_NETWORK: Default Kaspa network (mainnet, testnet-10, devnet, simnet)
• KASPA_LOG_LEVEL: Logging verbosity (off, error, warn, info, debug, trace)

Note: For security, avoid logging sensitive values. Prefer using per-session credentials or environment-based configurations that are not captured in logs.

Tips and common considerations:

• Always connect to the correct network before performing wallet actions or transactions (mainnet vs testnet variants).
• Use sessions (sessionId) to isolate wallets and network connections per client or user.
• For production, prefer kaspa_setup_preconfigured_wallet to load credentials from environment variables rather than exposing mnemonics in client configs.
• Address formats differ by network (kaspa:, kaspatest:, kaspadev:, kaspasim:); ensure the recipient address matches the connected network.
• Enable a sensible KASPA_LOG_LEVEL (e.g., info or warn) to balance observability with performance.
• Handle errors returned by tools with the MCP standardized error format to provide clear context to clients.