Vibetrader

etbars4stars

Official VibeTrader MCP server enabling AI agents to manage trading bots, portfolios, strategies, and market analysis via natural language.

Finance

Install Run on PlugMCP

GitHub

Run on PlugMCP

1# Vibetrader

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: MIT
Last checked: 2026-10-28

Stars: 4
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Vibetrader?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Vibetrader need an API key?

No required environment variable is listed on this record.

What transport does Vibetrader use?

Vibetrader runs locally over stdio.

When was Vibetrader last checked?

Last checked 2026-10-28. Official VibeTrader MCP server enabling AI agents to manage trading bots, portfolios, strategies, and market analysis via natural language.

From the publisher

Documentation

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 the market clock
Signal Mode: Bots that tell you what to trade at any brokerage, including ones VibeTrader can't trade such as Robinhood, and track the fills you report back
Backtesting: Test strategies on historical data

Available Tools

37 tools are available over either endpoint below. authenticate exists only over local stdio — hosted clients sign in instead (see Connect).

Tool	Description
`authenticate`	(local stdio only) Authenticate with your API key from vibetrader.markets/settings
`create_bot`	Create a new trading bot using natural language
`list_bots`	List all your trading bots
`search_bots`	Search for bots by name
`get_bot`	Get details of a specific bot
`update_bot`	Update a bot's name or status
`refine_bot`	Refine a bot's strategy using natural language
`start_bot`	Start a paused bot
`pause_bot`	Pause a running bot
`delete_bot`	Delete a bot
`start_all_bots`	Start all paused bots at once
`pause_all_bots`	Pause all running bots at once
`delete_all_bots`	Delete ALL bots (requires `confirm='DELETE ALL'`)
`get_bot_strategy`	Get the full strategy configuration for a bot
`explain_bot_strategy`	Get a plain English explanation of a bot's strategy
`get_bot_stats`	Get aggregate statistics across your bots
`get_daily_trade_stats`	Get daily trading statistics for a bot
`get_portfolio`	Get portfolio positions and balance
`get_positions`	Get current open positions with unrealized P&L
`get_account_summary`	Get account balance, buying power, and key metrics
`close_position`	Close a position by symbol (Alpaca account)
`place_order`	Place a buy or sell order (Alpaca account; a retry is never placed twice)
`get_trade_history`	Get recent trade history across all bots
`get_bot_trades`	Get trade history for a specific bot
`get_quote`	Get current quote for a stock
`list_indicators`	List every technical indicator bots can use, with parameters and outputs (no API key needed)
`get_market_status`	Check if US stock markets are currently open
`preview_bot`	Quick backtest of a bot, not saved, with the buy-and-hold comparison (window fits the strategy: 45 days to a year)
`run_backtest`	Run a historical backtest for a bot's current strategy
`list_backtests`	List all backtests for a bot
`get_backtest`	Get detailed results for a specific backtest
`quick_covered_call_backtest`	Run a quick covered call income strategy backtest
`set_signal_mode`	Switch a bot between placing its own trades and sending signals
`list_open_signals`	Signals waiting for you to place, across your signal bots
`report_signal`	Record what you did with a stock or crypto signal (bought, sold, skip, keep, undo)
`report_option_signal`	Record what you did with an option signal
`report_short_signal`	Record what you did with a short signal
`get_signal_state`	A signal bot's modes, books, results and recent signals

Endpoints

The hosted server speaks both MCP HTTP transports:

URL	Speaks
`https://mcp.vibetrader.markets/mcp`	Streamable HTTP — the current MCP transport. Use this one.
`https://mcp.vibetrader.markets/sse`	Either transport. A client that opens an SSE stream gets one (with its companion `/messages/` POST route, which the stream advertises — you never configure it by hand); a client that POSTs JSON-RPC gets streamable HTTP, the same session space as `/mcp`.

The original https://vibetrader-mcp-289016366682.us-central1.run.app/mcp and /sse URLs keep working, with sign-in too. Prefer /mcp for anything new: SSE is deprecated upstream.

Connect

Claude (claude.ai, Desktop, mobile) or ChatGPT: add a custom connector with https://mcp.vibetrader.markets/mcp and click Connect. You sign in to VibeTrader and choose what the assistant may do. No key to copy.

Claude Code:

claude mcp add --transport http vibetrader https://mcp.vibetrader.markets/mcp

mcp-remote (for clients that only run local servers) signs in the same way:

{
  "mcpServers": {
    "vibetrader": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.vibetrader.markets/mcp"]
    }
  }
}

Clients that send a key (Cursor, Windsurf, OpenClaw, scripts): create a key at https://vibetrader.markets/settings and send it as a header:

{
  "mcpServers": {
    "vibetrader": {
      "url": "https://mcp.vibetrader.markets/mcp",
      "headers": { "Authorization": "Bearer vt_YOUR_KEY" }
    }
  }
}

Permissions

Every connection — and every key — carries what the user allowed:

Permission	Covers
See (always)	bots, portfolio, trades, signals, backtests
Manage bots and signals	create, edit, start, pause and delete paper bots and signal bots; record trades made for a signal
Place orders and run live bots	`place_order`, `close_position`, and creating, starting or switching a bot onto a real-money account (off unless ticked)

The VibeTrader API enforces them on every request. A tool called outside them fails with a message saying how to allow it. Keys can instead have full API access for scripts (everything but account settings). Users disconnect an app in Settings → Connected apps.

A request without a token

Over HTTP every request needs Authorization: Bearer ... — a sign-in token or a vt_ key. Without one the server answers 401 with a WWW-Authenticate header pointing at /.well-known/oauth-protected-resource/mcp, which names https://api.vibetrader.markets as the sign-in server; that is what makes an assistant show Connect. Pasting a key into chat (the old authenticate step) is gone over HTTP; it remains for local stdio (python server.py stdio).

Signal mode: trade at any brokerage

place_order and close_position only reach your VibeTrader Alpaca account. For money anywhere else, put a bot in signal mode. It keeps watching the market and deciding, but sends you each entry and exit instead of trading:

set_signal_mode(bot_id, follow_account="manual") (pause the bot first)
list_open_signals(): what to buy or sell, how much, and near what price
Place the order with that brokerage's own tools. With Robinhood's MCP connected in the same assistant, the assistant can do this step too.
report_signal(bot_id, decision_id, "bought", qty, price) with the real fill, so the bot tracks your actual shares and results and sends the exits.

Signals also arrive by push, email or webhook, set up in the app.

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 --max-instances=1

Keep --max-instances=1: place_order's retry memory lives in the process.

Security

Every HTTP request needs a sign-in token or a key, read from that request's own Authorization header and stored nowhere — never shared between users
Sign-in is OAuth 2.1 with PKCE against VibeTrader's API; tokens last an hour, refresh tokens rotate, and disconnecting an app ends its access immediately
What a connection may do is enforced by the API, not just this server
All requests are made over HTTPS
Paper trading mode is default for safety
Every tool declares MCP annotations, so your client can run read-only tools without asking and confirm the ones that trade, start bots or delete
place_order gives the same order the same order id while retries keep coming within two minutes of the last try, so retrying a call (say, after a timeout) never places a second order. Pass idempotency_key to hold the id for as long as you like

Vibetrader

etbars4stars

Official VibeTrader MCP server enabling AI agents to manage trading bots, portfolios, strategies, and market analysis via natural language.

Finance

Install Run on PlugMCP

GitHub

Run on PlugMCP

1# Vibetrader

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: MIT
Last checked: 2026-10-28

Stars: 4
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Vibetrader?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Vibetrader need an API key?

No required environment variable is listed on this record.

What transport does Vibetrader use?

Vibetrader runs locally over stdio.

When was Vibetrader last checked?

Last checked 2026-10-28. Official VibeTrader MCP server enabling AI agents to manage trading bots, portfolios, strategies, and market analysis via natural language.

From the publisher

Documentation

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 the market clock
Signal Mode: Bots that tell you what to trade at any brokerage, including ones VibeTrader can't trade such as Robinhood, and track the fills you report back
Backtesting: Test strategies on historical data

Available Tools

37 tools are available over either endpoint below. authenticate exists only over local stdio — hosted clients sign in instead (see Connect).

Tool	Description
`authenticate`	(local stdio only) Authenticate with your API key from vibetrader.markets/settings
`create_bot`	Create a new trading bot using natural language
`list_bots`	List all your trading bots
`search_bots`	Search for bots by name
`get_bot`	Get details of a specific bot
`update_bot`	Update a bot's name or status
`refine_bot`	Refine a bot's strategy using natural language
`start_bot`	Start a paused bot
`pause_bot`	Pause a running bot
`delete_bot`	Delete a bot
`start_all_bots`	Start all paused bots at once
`pause_all_bots`	Pause all running bots at once
`delete_all_bots`	Delete ALL bots (requires `confirm='DELETE ALL'`)
`get_bot_strategy`	Get the full strategy configuration for a bot
`explain_bot_strategy`	Get a plain English explanation of a bot's strategy
`get_bot_stats`	Get aggregate statistics across your bots
`get_daily_trade_stats`	Get daily trading statistics for a bot
`get_portfolio`	Get portfolio positions and balance
`get_positions`	Get current open positions with unrealized P&L
`get_account_summary`	Get account balance, buying power, and key metrics
`close_position`	Close a position by symbol (Alpaca account)
`place_order`	Place a buy or sell order (Alpaca account; a retry is never placed twice)
`get_trade_history`	Get recent trade history across all bots
`get_bot_trades`	Get trade history for a specific bot
`get_quote`	Get current quote for a stock
`list_indicators`	List every technical indicator bots can use, with parameters and outputs (no API key needed)
`get_market_status`	Check if US stock markets are currently open
`preview_bot`	Quick backtest of a bot, not saved, with the buy-and-hold comparison (window fits the strategy: 45 days to a year)
`run_backtest`	Run a historical backtest for a bot's current strategy
`list_backtests`	List all backtests for a bot
`get_backtest`	Get detailed results for a specific backtest
`quick_covered_call_backtest`	Run a quick covered call income strategy backtest
`set_signal_mode`	Switch a bot between placing its own trades and sending signals
`list_open_signals`	Signals waiting for you to place, across your signal bots
`report_signal`	Record what you did with a stock or crypto signal (bought, sold, skip, keep, undo)
`report_option_signal`	Record what you did with an option signal
`report_short_signal`	Record what you did with a short signal
`get_signal_state`	A signal bot's modes, books, results and recent signals

Endpoints

The hosted server speaks both MCP HTTP transports:

URL	Speaks
`https://mcp.vibetrader.markets/mcp`	Streamable HTTP — the current MCP transport. Use this one.
`https://mcp.vibetrader.markets/sse`	Either transport. A client that opens an SSE stream gets one (with its companion `/messages/` POST route, which the stream advertises — you never configure it by hand); a client that POSTs JSON-RPC gets streamable HTTP, the same session space as `/mcp`.

The original https://vibetrader-mcp-289016366682.us-central1.run.app/mcp and /sse URLs keep working, with sign-in too. Prefer /mcp for anything new: SSE is deprecated upstream.

Connect

Claude Code:

claude mcp add --transport http vibetrader https://mcp.vibetrader.markets/mcp

mcp-remote (for clients that only run local servers) signs in the same way:

{
  "mcpServers": {
    "vibetrader": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.vibetrader.markets/mcp"]
    }
  }
}

Clients that send a key (Cursor, Windsurf, OpenClaw, scripts): create a key at https://vibetrader.markets/settings and send it as a header:

{
  "mcpServers": {
    "vibetrader": {
      "url": "https://mcp.vibetrader.markets/mcp",
      "headers": { "Authorization": "Bearer vt_YOUR_KEY" }
    }
  }
}

Permissions

Every connection — and every key — carries what the user allowed:

Permission	Covers
See (always)	bots, portfolio, trades, signals, backtests
Manage bots and signals	create, edit, start, pause and delete paper bots and signal bots; record trades made for a signal
Place orders and run live bots	`place_order`, `close_position`, and creating, starting or switching a bot onto a real-money account (off unless ticked)

A request without a token

Signal mode: trade at any brokerage

set_signal_mode(bot_id, follow_account="manual") (pause the bot first)
list_open_signals(): what to buy or sell, how much, and near what price
Place the order with that brokerage's own tools. With Robinhood's MCP connected in the same assistant, the assistant can do this step too.
report_signal(bot_id, decision_id, "bought", qty, price) with the real fill, so the bot tracks your actual shares and results and sends the exits.

Signals also arrive by push, email or webhook, set up in the app.

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 --max-instances=1

Keep --max-instances=1: place_order's retry memory lives in the process.

Security

Every HTTP request needs a sign-in token or a key, read from that request's own Authorization header and stored nowhere — never shared between users
Sign-in is OAuth 2.1 with PKCE against VibeTrader's API; tokens last an hour, refresh tokens rotate, and disconnecting an app ends its access immediately
What a connection may do is enforced by the API, not just this server
All requests are made over HTTPS
Paper trading mode is default for safety
Every tool declares MCP annotations, so your client can run read-only tools without asking and confirm the ones that trade, start bots or delete
place_order gives the same order the same order id while retries keep coming within two minutes of the last try, so retrying a call (say, after a timeout) never places a second order. Pass idempotency_key to hold the id for as long as you like