Quick Setup
1
Install httpcat-cli
Choose your preferred installation method:
- npx (Recommended for MCP)
- Global Install
- Homebrew
No installation needed! The MCP config will use npx to run httpcat automatically.
2
Get your private key
You’ll need a Base-compatible private key with USDC for trading.
3
Configure your MCP client
Follow the instructions below for your specific client.
4
Test the connection
Ask your AI assistant:If it responds with your ETH and USDC balances, you’re all set!
Cursor Configuration
Cursor supports MCP natively. Configure in your MCP settings:Location
- macOS/Linux:
~/.cursor/mcp_settings.json - Windows:
%APPDATA%\Cursor\mcp_settings.json
Configuration (npx)
Configuration (Global Install)
If you installed httpcat-cli globally:Using Environment Variables
Instead of hardcoding the private key:Restart Cursor
After saving the configuration, restart Cursor to load the MCP server.Claude Desktop Configuration
Claude Desktop (Anthropic’s official app) supports MCP.Location
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
Configuration (npx)
Configuration (Global Install)
Restart Claude Desktop
Quit Claude Desktop completely and restart to load the MCP server.Custom MCP Clients
For other MCP-compatible clients:Standard MCP Configuration
Programmatic Setup
If you’re building an MCP client:Environment Configuration
Available Environment Variables
Configure httpcat behavior via environment variables:| Variable | Description | Default |
|---|---|---|
HTTPCAT_PRIVATE_KEY | Your private key | Required |
HTTPCAT_NETWORK | Network: eip155:84532 (testnet) or eip155:8453 (mainnet) | Auto-detected |
HTTPCAT_AGENT_URL | Agent endpoint | https://agent.402.cat |
HTTPCAT_RPC_URL | Custom RPC URL | Base default |
Network Selection
- Base Sepolia (Testnet)
- Base (Mainnet)
- Testing and learning
- Free testnet USDC
- No financial risk
If you don’t specify
HTTPCAT_NETWORK, it will be auto-detected from your wallet’s transactions.Security Best Practices
Private Key Management
Private Key Management
DO:
- Use environment variables
- Use your MCP client’s secrets management
- Use different keys for testnet and mainnet
- Rotate keys regularly
- Commit keys to version control
- Hardcode keys in config files
- Share keys in screenshots
- Reuse keys across projects
Environment Variables
Environment Variables
Best approach:
-
Create a
.envfile (add to.gitignore): -
Load in your shell:
-
Reference in MCP config:
Testing Setup
Testing Setup
Always test with testnet first:
- Use Base Sepolia network
- Get free testnet tokens from faucets
- Verify tools work correctly
- Then switch to mainnet with real funds
Backup & Recovery
Backup & Recovery
- Back up your seed phrase (not private key)
- Store offline in secure location
- Never share with anyone
- Consider hardware wallet for mainnet
Verifying Setup
Test Connection
Ask your AI assistant to run a health check:Test Balance
Test Token Info
Troubleshooting
MCP server not found
MCP server not found
Symptoms: AI assistant says httpcat tools are unavailableSolutions:
- Restart your MCP client completely
- Verify config file location
- Check command path:
- Check MCP client logs for errors
Private key errors
Private key errors
Symptoms: “Invalid private key” or “Authentication failed”Solutions:
- Verify key format starts with
0x - Ensure key is 64 hex characters (+
0xprefix) - Check environment variable is set:
- Try hardcoding temporarily to test
Network connection errors
Network connection errors
Symptoms: “Cannot connect to agent” or timeout errorsSolutions:
- Check internet connection
- Verify agent URL is reachable:
- Check for firewall/proxy issues
- Try custom agent URL if needed
Tool execution failures
Tool execution failures
Symptoms: Tools return errors or unexpected resultsSolutions:
- Check wallet has USDC for operations
- Check wallet has ETH for gas fees
- Verify network matches your funds
- Try the same operation via CLI:
- Check httpcat-cli logs
Version mismatch
Version mismatch
Symptoms: Tools behave differently than documentedSolutions:
- Update to latest version:
- For npx, it auto-updates on each run
- Check version:
- Clear npm cache if needed: