Connect a broker
Link a supported broker in BotSpot and use it from your preferred AI app.
ChatGPT broker connection guide
Connect ChatGPT to your broker through BotSpot. Link your account, review balances and positions, and request trades for approval. Sign in with BotSpot; no API key is needed.
Link a supported broker in BotSpot and use it from your preferred AI app.
Ask what is connected and what you hold, without building a strategy.
Review the account and order details, approve submission, then check the broker status.
ChatGPT does not connect directly to your broker in this workflow. ChatGPT connects to BotSpot, and BotSpot connects separately to a supported brokerage account.
Keep broker credentials, API keys, private keys, and passwords out of ChatGPT prompts. Use BotSpot broker settings for brokerage authentication and BotSpot OAuth for the ChatGPT connection.
Open BotSpot Broker Connections and select the broker, authentication method, and paper or live mode supported by your account. Broker support, asset classes, authentication methods, and modes can change, so verify the current broker page before continuing.
The current BotSpot manifest lists Alpaca, Charles Schwab, Tradier, Tradovate, Kraken, Coinbase, WEEX, Bitunix, and TopstepX. These connections do not support identical assets or account modes.
Open ChatGPT Plugins, choose + → Add custom MCP server, name it BotSpot and select Server URL. Use https://mcp.botspot.trade/mcp with OAuth, complete BotSpot sign-in, then select @BotSpot in a new chat. Availability depends on your plan and workspace permissions.
Begin with requests that inspect data without changing broker or deployment state. Confirm that ChatGPT reaches the intended BotSpot user, brokerage connection, account, and trading mode.
Do not infer live readiness from a successful MCP connection. MCP connectivity proves tool access, not broker permissions, strategy correctness, order eligibility, or execution quality.
When direct trading is enabled, ChatGPT can ask BotSpot to prepare a supported one-time order. BotSpot presents the action for review and explicit confirmation before submission.
MCP-driven start, stop, update, and trade requests use action-specific authorization. BotSpot checks ownership and may require a fresh login. A recent login can reduce repeated credential prompts, but it never approves or batches actions automatically.
Review symbol, side, quantity, order type, account, broker, and paper or live mode on the BotSpot authorization page. Reject any action that differs from your request.
Tell ChatGPT which BotSpot tool boundary applies. Separate research, strategy changes, backtesting, deployment, and trading instead of combining them into one broad instruction.
After completing the linked ChatGPT setup, start with account inspection. BotSpot OAuth connects the client to BotSpot; the broker connection and account mode are managed separately inside BotSpot.
OAuth access does not make AI-generated instructions trustworthy. Prompt injection, ambiguous requests, stale context, software defects, broker restrictions, and market conditions can all produce unsafe or invalid actions.
Never paste brokerage secrets into chat. Inspect every authorization request and monitor positions, orders, balances, and deployed strategies through the broker and BotSpot.
No. ChatGPT connects to BotSpot through OAuth MCP. Your supported brokerage account connects separately inside BotSpot.
No. ChatGPT uses BotSpot OAuth for this connection. Enter brokerage credentials only through the appropriate BotSpot broker connection flow.
BotSpot supports approved one-time trading actions when direct trading is enabled. The user must review and explicitly approve the action. Automated strategy deployment is a separate reviewed workflow.
Use the current BotSpot broker directory and public manifest. Each broker supports different assets, authentication methods, paper or live modes, regions, and account permissions.
OpenAI documents that Developer mode availability can depend on account access and workspace policy. A workspace administrator may need to enable the required access.
Sources verified 2026-08-14.
Past performance does not guarantee future results. Automated trading involves risk of loss.