Claude Desktop
Developer integration guide — connect GoldenClaw to Claude Desktop via MCP.
Prerequisites
- GoldenClaw API key (create one here)
- Claude Desktop installed
Setup
1. Open Config File
Open the Claude Desktop configuration file in your text editor:
macOS
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows
%APPDATA%\Claude\claude_desktop_config.jsonLinux
~/.config/Claude/claude_desktop_config.jsonIf the file doesn't exist, create it.
2. Add GoldenClaw Server
Add the following to your config file:
{
"mcpServers": {
"goldenclaw": {
"url": "https://stage.goldenclaw.sh/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Replace YOUR_API_KEY with your actual API key.
Existing servers
If you already have other MCP servers configured, add goldenclaw alongside them inside the mcpServers object.
3. Restart Claude Desktop
Close and reopen Claude Desktop for the changes to take effect.
4. Verify Connection
Start a new conversation and type:
"What's the current BTC/USDT price on Binance futures?"
You should see Claude use the get_price tool and return the current price.
Example Prompts
"Calculate RSI for ETH/USDT on the 4h timeframe on Bybit"
"What are my open positions on Binance futures?"
"Show me Bollinger Bands for SOL/USDT on OKX"
"Analyze BTC/USDT: get price, RSI, and MACD on the 4h chart"
Available Tools
| Category | Tools |
|---|---|
| Market Data | get_price, get_ohlcv, get_ticker, get_pairs, get_symbols, get_timeframes |
| Trading | place_order, cancel_order, get_orders, get_positions, close_position |
| Account | get_balance, get_account |
| Analysis | calculate_indicator (35+ indicators) |
| Discovery | list_exchanges |
See MCP Tools for full tool documentation.
Troubleshooting
"Connection refused" or "Server not found"
Check that the URL is exactly https://stage.goldenclaw.sh/mcp and your config file is valid JSON.
"Unauthorized" error
Your API key may have expired or been revoked. Generate a new one from your Dashboard.
Tools not appearing
Restart Claude Desktop after saving the config file. Check that the JSON syntax is correct — a missing comma or bracket will silently fail.