@blueprintaix/blueprint-mcp
Official# @blueprintaix/blueprint-mcp
An MCP server that connects AI assistants to DeFi yield opportunities across EVM and Solana chains. Discover, evaluate, and execute yield strategies through natural conversation—with transactions signed locally on your machine.
## Features
- **Multi-chain support** — Base (EVM) and Solana, with more chains coming soon
- **Local signing** — Private keys never leave your machine
- **MCP integration** — Works with Claude Desktop and other MCP-compatible clients
- **Intent execution** — Automatically signs and submits transactions
## Quick Start
Add the following to your Claude Desktop configuration:
**macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`
**Linux:** `~/.config/Claude/claude_desktop_config.json`
```json
{
"mcpServers": {
"blueprint": {
"command": "npx",
"args": ["-y", "@blueprintaix/blueprint-mcp"],
"env": {
"BLUEPRINT_API_KEY": "<your-api-key>",
"EVM_PRIVATE_KEY": "<your-evm-private-key>",
"SOLANA_PRIVATE_KEY": "<your-solana-private-key>"
}
}
}
}
```
## Configuration
| Variable | Required | Description |
|----------|----------|-------------|
| `BLUEPRINT_API_KEY` | No | API key for Blueprint services (see below for x402 fallback) |
| `EVM_PRIVATE_KEY` | One required | Private key for EVM transactions |
| `SOLANA_PRIVATE_KEY` | One required | Private key for Solana transactions (base58) |
| `BASE_RPC_URL` | No | Custom Base RPC endpoint |
| `SOLANA_RPC_URL` | No | Custom Solana RPC endpoint |
> At least one of `EVM_PRIVATE_KEY` or `SOLANA_PRIVATE_KEY` must be provided.
### x402 Payment Fallback
If no `BLUEPRINT_API_KEY` is provided, the MCP SDK will automatically fall back to using [x402](https://www.x402.org/) for making payments to call tools. Payments are made on **Base** using **USDC**.
When using x402 payments, `EVM_PRIVATE_KEY` is required to sign the payment transactions.
## Get an API Key
Contact **meet@emberlabs.io** to request a Blueprint API key, or use x402 payments as described above.
## Troubleshooting
**Server doesnt start?** Check the following:
1. **Missing private key for x402** — If using x402 payments (no `BLUEPRINT_API_KEY`), ensure `EVM_PRIVATE_KEY` is set
2. **Invalid private key format:**
- `EVM_PRIVATE_KEY` must start with `0x` (66 characters total)
- `SOLANA_PRIVATE_KEY` must be base58-encoded (~88 characters)
3. **Cached package issue** — Clear the npx cache and restart:
```bash
rm -rf ~/.npm/_npx
```
**Still stuck?** Check the MCP logs in Claude Desktop (~/Library/Logs/Claude/ mcp-server-bp.log)
## License
MIT
TDQS
Scored across 15 tools
Most tools have clearly distinct purposes, especially the chain-specific vault operations (Solana, EVM, Sui). Minor ambiguity exists between find-tokens and fetch-tokens, and between fetch-vault-analytics and fetch-vaults, but the descriptions provide sufficient guidance.
Naming is inconsistent, mixing hyphenated names (find-tokens, solana-deposit-to-vault) with underscored names (get_wallet_address, execute_intent). Also, both 'fetch' and 'get' are used as verbs, and there is no uniform pattern across chain-specific and generic tools.
15 tools is well-scoped for a multi-chain vault management server. Each tool serves a necessary function, covering three chains with fetch/deposit/withdraw operations plus supporting utilities for tokens, analytics, wallet address, and intent execution.
The core lifecycle is covered: fetching vaults, depositing, withdrawing, and analytics. Minor gaps exist, such as the lack of a complete-withdraw tool for EVM and Sui chains (only Solana has it) and no explicit portfolio/balance tool, but agents can work around these.