@gt-protocol/mcp

GT Protocol MCP Server — connect Claude, Cursor, Claude Code, or any MCP-compatible AI agent to your GT Protocol trading account.

Manage bots, run backtests, check balances, and automate trading strategies — all through natural language.

What is MCP?

Model Context Protocol is an open standard that lets AI agents call external tools. This server exposes the GT Protocol REST API as a set of tools that any MCP-compatible AI can use.

---

Quickstart

1. Add to Claude Code

Add this to your .mcp.json (or ~/.claude.json for global access):

{
  "mcpServers": {
    "gt-protocol": {
      "command": "node",
      "args": ["/path/to/gt-protocol/mcp-server/index.js"]
    }
  }
}

No env variables needed.

2. Authenticate

On first use, call the authenticate tool:

Authenticate with GT Protocol using email@example.com and my password

The server calls /auth/sign_in, saves tokens to ~/.gt-mcp-auth.json, and confirms with your account email.

Tokens auto-refresh as long as you use the server at least once every 7 days. After 7 days of total inactivity, call authenticate again.

Signed up with Google? You don't have a password. Open the GT Protocol web app, open DevTools → Application → Local Storage, copy access_token and refresh_token, and add them to .mcp.json as env vars:

"env": {
  "GT_TOKEN": "<access_token>",
  "GT_REFRESH_TOKEN": "<refresh_token>"
}

The server will pick them up on startup and auto-refresh from there.

3. Start trading with AI

List my active bots
What's my Binance balance?
Create a BTC/USDT long bot with $50 start order and 2% take profit
Close the deal on bot 12345
Run a backtest for ETH/USDT with MACD strategy, 3% TP, 1% SL

---

Available Tools

Auth

Tool	Description
authenticate	Sign in with email + password. Call once — tokens persist to disk and auto-refresh.

Bots

Tool	Description
list_bots	List standalone strategies/bots. Does NOT include Portfolio strategies — call list_portfolios for those.
list_portfolios	List Portfolio strategies (multi-bot baskets). Each portfolio occupies its exchange: a portfolio on Binance blocks any new standalone SPOT bot on that account. Always call together with list_bots when auditing exchange usage.
get_bot	Get details of a specific bot
create_bot	Create a new trading bot
update_bot	Update bot settings
start_bot	Activate a bot
stop_bot	Deactivate a bot
delete_bot	Archive (soft-delete) a bot. Requires no active deal — close it first with close_deal if open.
paper_clone	Create a paper trading copy of a live bot

Deals

Tool	Description
start_deal	Manually open a deal on an active bot immediately (skip signal wait)
close_deal	Market-close the active deal on a bot
list_deals	List all deals (open + closed), filter by bot
get_active_deals	Get all currently active deals
get_deal_history	Closed deals with profit stats

Account

Tool	Description
get_exchanges	List connected exchange accounts
get_balance	Get balance for an exchange account
get_profile	Current user profile and stats

Backtest

Tool	Description
run_backtest	Run a backtest on historical data. Strategies: macd, bollinger, kdj. Returns win rate, PnL, drawdown, full trade list.

Note: Backtest requests are routed through a proxy. The proxy key is fetched automatically after authenticate — no extra env vars needed.

---

Examples

Morning portfolio check

What's the status of all my bots? Which ones have active deals?
Show me my total profit this week.
What's my available USDT balance on Binance?

Strategy research

Run a backtest for BTC/USDT on Binance with bollinger strategy,
long direction, 2.5% TP, 1% SL, 5m timeframe, last 30 days.
Compare with MACD strategy same params.

Bot management

Stop all my losing bots (those with negative total profit).
Update bot 12345 — increase take profit to 3% and add a 5% stop loss.
Start a deal on bot 12345 right now without waiting for a signal.

---

Paper Trading

GT Protocol supports paper (demo) trading — test strategies without real capital.

• Set paper: true in create_bot to create a demo bot from scratch
• Use paper_clone to copy an existing live bot into demo mode

Paper bots run on real market data but don't place real orders.

---

Authentication Details

Tokens are stored in ~/.gt-mcp-auth.json after the first authenticate call.

Token	TTL	Behavior
Access token	~1 hour	Auto-refreshed on 401 responses
Refresh token	~7 days	Used to get new access tokens silently

When the refresh token expires (~7 days of total inactivity), call authenticate again. Normal usage keeps tokens alive indefinitely through automatic refresh.

You can still set GT_TOKEN / GT_REFRESH_TOKEN in .mcp.json env to override the saved tokens — useful for CI/automation.

Environment variables

Variable	Default	Description
GT_TOKEN	—	Override access token (optional)
GT_REFRESH_TOKEN	—	Override refresh token (optional)
GT_API_URL	http://46.225.216.13:8765	Override API base URL
GT_PROXY_URL	http://46.225.216.13:8081	Backtest proxy URL
GT_PROXY_API_KEY	—	Override backtest proxy key (fetched automatically after authenticate)

---

Supported Exchanges

• Binance (SPOT + FUTURES)
• Hyperliquid (FUTURES)

---

Requirements

• Node.js 18+ (dependencies are bundled — no npm install needed)
• A GT Protocol account — sign up at gt-protocol.io
• A connected exchange account (Binance or Hyperliquid)

---

License

MIT — free to use, fork, and extend.

Built by GT Protocol.