Crypto MCP Server provides a local, lightweight dashboard and REST/WebSocket backend that proxies a collection of MCP tools (CCXT for exchange data and trading, CoinGecko for price data, a portfolio aggregator, and more such as Freqtrade) to Claude Desktop and local MCP clients. The server runs alongside a React frontend dashboard that lets you monitor ticker data, portfolio balances, and orders, with live updates via Socket.io. It exposes REST endpoints like /api/ticker, /api/portfolio, /api/order/dry_run, /api/order/execute, and /api/orders, and stores a local log of orders in SQLite. To use it, install the backend and frontend as described, start the backend service (crypto-mcp-gui), and then access the dashboard UI to visualize data and perform dry-runs or live trades through the configured MCP endpoints.

Prerequisites:

• A Linux-based system (e.g., Raspberry Pi) with bash and curl
• Node.js installed (or install via the provided script)
• Git (optional for cloning)

Recommended automated installation (quickstart):

1. Save the installer as instructed:

   • Place install.sh into /home/pelle/install.sh (or /home/pelle/cryptomcpserver/install.sh)
   • Ensure it is executable: chmod +x /home/pelle/install.sh

2. Run the installer: cd /home/pelle ./install.sh

If you prefer manual installation:

1. Install system dependencies: sudo apt update sudo apt install -y curl build-essential ca-certificates git

2. Install Node.js (if needed): curl -sL https://deb.nodesource.com/setup_20.x | sudo -E bash - sudo apt install -y nodejs node -v

3. Backend setup: cd /home/pelle/cryptomcpserver/gui/backend

   place server.js and package.json here, then:

   npm install cp .env.example .env

   Edit .env if needed

4. Frontend setup (optional for development): cd /home/pelle/cryptomcpserver/gui/frontend npm install npm run dev -- --host # open http://PI_IP:5173 on your laptop

5. Systemd service for backend (production):

   Create /etc/systemd/system/crypto-mcp-gui.service (see README for content)

   sudo systemctl daemon-reload sudo systemctl enable --now crypto-mcp-gui.service

6. Start the backend and check status: sudo systemctl status crypto-mcp-gui.service sudo journalctl -u crypto-mcp-gui.service -f

Notes:

• Backend listens on port 4000 by default as configured in .env (PORT=4000).
• MCP endpoints expected by Claude Desktop are set in .env (MCP_CCXT and MCP_PORTFOLIO).

Environment variables and configuration tips:

• MCP_CCXT: URL to the CCXT MCP endpoint (e.g., http://127.0.0.1:7001/mcp)
• MCP_PORTFOLIO: URL to the portfolio MCP (optional; e.g., http://127.0.0.1:7004/mcp)
• PORT: backend listening port (default 4000)
• Ensure the backend systemd service crypto-mcp-gui.service is enabled to start at boot.
• If you see port conflicts, the installer will free port 4000 as needed.
• REST and WebSocket endpoints are used by Claude Desktop Local MCP integration to call tools like get_ticker, create_order, and others. Expose these endpoints only on trusted networks or with appropriate security measures.
• Frontend assets are served from the backend; for development, you can run the frontend separately with npm run dev.