Kaspa MCP Server
Model Context Protocol server for Kaspa operations using WASM SDK. Enables LLMs to interact with the Kaspa network through standardized MCP tools.
README
Kaspa MCP Server
Model Context Protocol server for Kaspa operations using WASM SDK. Enables LLMs to interact with the Kaspa network through standardized MCP tools.
Features
- ๐ Connect to different Kaspa networks (mainnet, testnet-10, devnet, simnet)
- ๐ Wallet Management - Create, import, and manage HD wallets
- ๐ฐ Balance Checking - Get balance and UTXO information
- ๐ค Send Transactions - Send KAS with optional payloads/messages
- ๐ Fee Estimation - Calculate transaction fees
- ๐ Address Validation - Validate Kaspa addresses
- ๐ฒ Mnemonic Generation - Generate secure wallet mnemonics
Setup
npm run install-all
npm run build
Environment Variables
The MCP server supports several environment variables for configuration:
Network Configuration
KASPA_DEFAULT_NETWORK: Default network to use (mainnet,testnet-10,devnet,simnet)KASPA_MAINNET_RPC_URL: Custom mainnet RPC endpointKASPA_TESTNET_RPC_URL: Custom testnet RPC endpointKASPA_LOG_LEVEL: Logging level (off,error,warn,info,debug,trace)
Wallet Configuration (Secure)
KASPA_WALLET_MNEMONIC: Preconfigured wallet mnemonic phrase (12-24 words)KASPA_WALLET_PRIVATE_KEY: Preconfigured wallet private key (hex format)
Security Note: Use environment variables to keep sensitive wallet credentials away from AI agents and conversation logs.
Example .env file
KASPA_DEFAULT_NETWORK=testnet-10
KASPA_TESTNET_RPC_URL=wss://photon-10.kaspa.red/kaspa/testnet-10/wrpc/borsh
KASPA_WALLET_MNEMONIC="your twelve word mnemonic phrase here for testnet use only"
KASPA_LOG_LEVEL=info
Usage
As MCP Server
Add to your MCP client configuration:
Basic Configuration
{
"mcpServers": {
"kaspa": {
"command": "node",
"args": ["/path/to/kaspa-mcp-server/dist/index.js"]
}
}
}
Note: The configuration field name varies by MCP client:
- Claude Desktop: Use
"mcpServers" - Other MCP clients: May use
"servers"or"mcp_servers" - Custom implementations: Check your client's documentation for the correct field name
Configuration with Preconfigured Wallet (Recommended)
For secure operation with environment variables:
{
"mcpServers": {
"kaspa": {
"command": "node",
"args": ["/path/to/kaspa-mcp-server/dist/index.js"],
"env": {
"KASPA_WALLET_MNEMONIC": "abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon about",
"KASPA_DEFAULT_NETWORK": "testnet-10",
"KASPA_LOG_LEVEL": "info"
}
}
}
}
Security Note: Replace the example mnemonic with your own wallet's mnemonic phrase. This keeps your wallet credentials secure and away from AI conversation logs.
Development
npm run dev
Available Tools
1. ๐ kaspa_connect (STEP 1)
Connect to a Kaspa network. This must be called first before using any wallet or transaction tools.
Parameters:
network(required): Network type (mainnet,testnet-10,devnet,simnet) - Usetestnet-10for testingrpcUrl(optional): Custom RPC endpointsessionId(optional): Session identifier (default:default)
Example:
{
"name": "kaspa_connect",
"arguments": {
"network": "testnet-10",
"sessionId": "my-session"
}
}
2. kaspa_create_wallet
Create or import a Kaspa wallet.
Parameters:
sessionId(optional): Session identifiermnemonic(optional): Import from mnemonic phraseprivateKey(optional): Import from private key
Example:
{
"name": "kaspa_create_wallet",
"arguments": {
"sessionId": "my-session"
}
}
3. kaspa_get_balance
Get balance for a Kaspa address.
Parameters:
address(required): Kaspa address to checksessionId(optional): Session identifier
Example:
{
"name": "kaspa_get_balance",
"arguments": {
"address": "kaspa:qq..."
}
}
4. kaspa_send_transaction
Send a Kaspa transaction.
Parameters:
from(required): Sender addressto(required): Recipient addressamount(required): Amount in KAS (e.g., "1.5")priorityFee(optional): Priority fee in KASpayload(optional): Message/data to attachsessionId(optional): Session identifier
Example:
{
"name": "kaspa_send_transaction",
"arguments": {
"from": "kaspa:qq...",
"to": "kaspa:qr...",
"amount": "1.5",
"payload": "Payment for services"
}
}
5. kaspa_estimate_fee
Estimate transaction fees.
Parameters:
from(required): Sender addressto(required): Recipient addressamount(required): Amount in KASsessionId(optional): Session identifier
6. kaspa_generate_mnemonic
Generate a new mnemonic phrase.
Parameters:
wordCount(optional): Number of words (12, 15, 18, 21, 24)
7. kaspa_validate_address
Validate a Kaspa address.
Parameters:
address(required): Address to validatenetwork(optional): Network for validation
8. kaspa_setup_preconfigured_wallet
Setup wallet using preconfigured credentials from environment variables.
Parameters:
sessionId(optional): Session identifier
Environment Variables Required:
KASPA_WALLET_MNEMONIC: 12-24 word mnemonic phraseKASPA_WALLET_PRIVATE_KEY: Private key in hex format
Example:
{
"name": "kaspa_setup_preconfigured_wallet",
"arguments": {}
}
9. kaspa_get_wallet_info
Get wallet information.
Parameters:
sessionId(optional): Session identifier
Session Management
The server supports multiple concurrent sessions using sessionId parameters. Each session maintains its own:
- Network connection
- Wallet instance
- Configuration
Security Notes
- ๐ Never log or expose private keys or mnemonics
- ๐ Use testnet for development and testing
- ๐พ Wallet credentials are kept in memory only (not persisted)
- ๐งน Resources are automatically cleaned up on server shutdown
- ๐ Preconfigured Wallets: Use environment variables to keep sensitive credentials away from AI agents
- โ ๏ธ Environment Security: Ensure your .env files are not committed to version control
Network Endpoints
Default endpoints:
- Mainnet:
ws://seeder2.kaspad.net:17110โ Public endpoint - Testnet-10:
wss://photon-10.kaspa.red/kaspa/testnet-10/wrpc/borshโ Public endpoint - Devnet:
ws://127.0.0.1:16610(requires local node) - Simnet:
ws://127.0.0.1:16510(requires local node)
Address Formats by Network
- Mainnet addresses: Start with
kaspa:(e.g.,kaspa:qz...) - Testnet addresses: Start with
kaspatest:(e.g.,kaspatest:qr...) - Devnet addresses: Start with
kaspadev:(e.g.,kaspadev:qp...) - Simnet addresses: Start with
kaspasim:(e.g.,kaspasim:qq...)
โ ๏ธ Important: Addresses are network-specific. You cannot send from a mainnet wallet to a testnet address or vice versa.
Error Handling
All tools return structured error messages with:
- Error code (following MCP standards)
- Descriptive error message
- Context about the failure
Examples
Basic Workflow
- Connect to testnet:
{"name": "kaspa_connect", "arguments": {"network": "testnet-10"}}
- Create a wallet:
{"name": "kaspa_create_wallet", "arguments": {}}
- Check balance:
{"name": "kaspa_get_balance", "arguments": {"address": "kaspatest:qq..."}}
- Send transaction:
{
"name": "kaspa_send_transaction",
"arguments": {
"from": "kaspatest:qq...",
"to": "kaspatest:qr...",
"amount": "0.1",
"payload": "Test transaction from MCP"
}
}
Secure Workflow (Preconfigured Wallet)
When using the preconfigured wallet configuration (with environment variables in your MCP client config):
- Setup preconfigured wallet:
{"name": "kaspa_setup_preconfigured_wallet", "arguments": {}}
- Get wallet info:
{"name": "kaspa_get_wallet_info", "arguments": {}}
- Send transaction (no private keys exposed to AI):
{
"name": "kaspa_send_from_wallet",
"arguments": {
"to": "kaspatest:qr...",
"amount": "0.1",
"feePriority": "normal",
"payload": "Optional message"
}
}
Benefits:
- ๐ Secure: Private credentials never appear in AI conversation logs
- โก Fast: No need to manually connect or create wallets each time
- ๐ Consistent: Same wallet used across sessions
- ๐ก๏ธ Safe: Environment variables keep sensitive data away from AI agents
Development
# Install all dependencies (workspace + nested packages)
npm run install-all
# Build everything (SDK first, then MCP server)
npm run build
# Development mode
npm run dev
# Run production server
npm start
# Clean build artifacts
npm run clean
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.