casper-network

The Casper Network MCP Server provided here exposes a dual-server setup: an HTTP Express server for REST API access and an MCP stdio server that integrates with Claude Desktop for seamless AI-assisted interactions. It implements the MCP protocol 2024-11-05 and is tightly integrated with the Casper blockchain, offering a suite of blockchain tools such as wallet creation, balance checks, token transfers, and staking operations. You can access the REST endpoints for programmatic control and use the MCP stdio channel to interact with Claude Desktop for conversational prompts that drive on-chain actions. The included tools.js module exposes a collection of Casper-related commands (e.g., create_wallet, get_balance, transfer_cspr, delegate_stake, undelegate_stake, get_staking_rewards, get_validator_info) that can be invoked via a JSON-RPC interface. To start, configure your environment with a Casper API key and network endpoint, then run the HTTP server and the MCP stdio bridge to enable full capability.

Prerequisites:

• Node.js >= 18.0.0
• npm >= 9.0.0
• Access to a Casper Network API key from cspr.cloud

Installation steps:

1. Clone the repository

git clone https://github.com/Tairon-ai/casper-network-mcp.git
cd casper-network-mcp

2. Install dependencies

npm install

3. Configure environment

cp .env.example .env

Note: In this MCP project, the environment variables required include CASPER_API_KEY, CASPER_RPC_URL, CASPER_NETWORK_NAME, and PORT. Populate them in the .env file or rely on the defaults if provided by the code. 4) Start the HTTP server

npm start

5. Start the MCP stdio server for Claude Desktop integration

npm run mcp

6. If you want to run via the MCP config, ensure the path to the MCP entry script is correct in your mcp_config and start your process manager or run the node command accordingly.

Optional: Run production optimizations

NODE_ENV=production npm start

Environment variables and security:

• Never commit .env files or private keys to version control.
• Store sensitive data (API keys, private keys) in environment variables and use access-controlled secret managers in production.
• The server operates on Casper mainnet; exercise caution with real CSPR tokens.
• Validate all public keys, addresses, and amounts before processing transactions.
• If using Docker, ensure the environment file (.env) is mounted and accessible inside the container.
• The MCP tools expose powerful operations (wallet creation, transfers, and staking); implement proper access controls when exposing these via HTTP endpoints.