VibeTrader MCP Server

A Model Context Protocol (MCP) server that connects AI assistants like Claude Desktop, Cursor, and Windsurf to VibeTrader's trading platform.

Features

• Create Bots: Create AI-powered trading bots using natural language
• Manage Bots: Start, pause, delete, and monitor your bots
• Portfolio: View positions and account balance
• Market Data: Get quotes and options chains
• Backtesting: Test strategies on historical data

Available Tools

All 30 are available over either endpoint below.

Endpoints

The hosted server speaks both MCP HTTP transports:

Both URLs expose the same 30 tools and the same authentication, so an existing /sse setup keeps working as-is. Prefer /mcp for anything new: SSE is deprecated upstream, and /sse is kept working for setups copied from older versions of this README.

Setup for Claude Desktop

1. Get your API token from https://vibetrader.markets/settings

2. Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "vibetrader": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://vibetrader-mcp-289016366682.us-central1.run.app/mcp"]
    }
  }
}

Clients that connect to a remote MCP URL directly (Cursor, Windsurf, and Claude Desktop's own remote-server support) can use the URL on its own:

{
  "mcpServers": {
    "vibetrader": {
      "url": "https://vibetrader-mcp-289016366682.us-central1.run.app/mcp"
    }
  }
}

/sse works too — see Endpoints — but /mcp is the one to use for a new setup.

1. Send your token as a header. Against the hosted server this is how you authenticate — see the note below:

{
  "mcpServers": {
    "vibetrader": {
      "url": "https://vibetrader-mcp-289016366682.us-central1.run.app/mcp",
      "headers": { "Authorization": "Bearer vt_YOUR_TOKEN" }
    }
  }
}

1. Restart Claude Desktop

2. Create bots:

   "Create a trading bot that buys AAPL when RSI goes below 30"

A note on the authenticate tool

There is an authenticate tool, and over a local stdio setup (python server.py stdio) it does what you would expect: hand it your token once and the rest of the session is authenticated.

Over HTTP — which is every hosted setup above — use the Authorization header instead. The header is resolved per request and stored nowhere, so it is also the safer of the two: the server never holds your token at all.

Example Conversations

Create a momentum bot:

"Create a trading bot that buys AAPL when RSI crosses below 30 and sells when it crosses above 70"

Check your bots:

"Show me all my trading bots and their performance"

Backtest a strategy:

"Backtest a moving average crossover strategy on SPY for the last 6 months"

Options trading:

"Create an iron condor bot for SPY that enters when IV rank is above 50"

Development

# Install dependencies
pip install -r requirements.txt

# Run locally (HTTP mode — serves both /mcp and /sse on :8080,
# the same app the deployment runs)
python server.py

# ...or exactly as the container does
uvicorn server:app --host 0.0.0.0 --port 8080

# Run in STDIO mode (for a local Claude Desktop install)
python server.py stdio

Then point a client at http://localhost:8080/mcp or http://localhost:8080/sse.

Deployment

Deployed on Google Cloud Run at mcp.vibetrader.markets

gcloud run deploy vibetrader-mcp --source . --region us-central1

Security

• Your API token is required for authentication
• All requests are made over HTTPS
• Tokens are resolved per request and never shared between users: over HTTP the Authorization: Bearer vt_... header is read from your own request and stored nowhere at all
• Paper trading mode is default for safety