MCP for Agents
Use BotSpot from ChatGPT, Claude, Claude Code, Codex, Gemini CLI, Cursor, or another MCP-compatible client.
Wire contract: MCP 2026-07-28 over stateless HTTP POST. Current clients negotiate this automatically.
Setup guides
Connect from the AI tool you already use
Every guide is visible on this page so people and AI assistants can read the complete setup without opening tabs.
OAuth connector
ChatGPT
- Best for
- Asking ChatGPT to inspect BotSpot strategies, broker context, backtests, and deployment state.
- Authentication
- OAuth
- Enable developer modeUse ChatGPT on the web. Open Settings -> Security and login, then enable Developer mode. Availability can depend on account and workspace policy.
- Add BotSpotOpen ChatGPT Plugins, select the plus button, and create a connection named BotSpot.
- Enter server URLChoose the public server URL connection method and paste
https://mcp.botspot.trade/mcp. Keep the complete/mcppath. - AuthorizeCreate the connection, complete BotSpot OAuth when prompted, then review the discovered tools and confirmation behavior.
- Use it in chatStart a new chat and select BotSpot from the tools menu, or refer to BotSpot in your prompt.
Server URL
https://mcp.botspot.trade/mcpRemote MCP
Claude
- Best for
- Keeping Claude connected to the same BotSpot strategy and execution context you use in the app.
- Authentication
- OAuth
- Add BotSpotIndividual users open Customize -> Connectors, click + -> Add custom connector and paste the MCP host URL. Team and Enterprise owners add it first under Organization settings -> Connectors.
- AuthorizeComplete OAuth, then enable BotSpot for the conversation from + -> Connectors.
Server URL
https://mcp.botspot.tradeCLI setup
Claude Code
- Best for
- Working from a terminal while still referencing your BotSpot library, revisions, and backtest evidence.
- Authentication
- BotSpot API key
- Create a keyCreate a BotSpot API key and export it as
BOTSPOT_API_KEY. - Install MCPRun the command below from your shell.
claude mcp add --transport http botspot https://mcp.botspot.trade/mcp --header "Authorization: Bearer $BOTSPOT_API_KEY"CLI, desktop, and IDE setup
Codex
- Best for
- Researching markets and working with your BotSpot strategies, revisions, and backtest evidence from Codex.
- Authentication
- BotSpot API key
- Create a keyCreate a BotSpot API key and export it as
BOTSPOT_API_KEY. - Configure BotSpotAdd the configuration below to
~/.codex/config.tomlor a trusted project's.codex/config.toml. - Confirm the connectionOpen Codex and use
/mcp, or runcodex mcp list.
[mcp_servers.botspot]
url = "https://mcp.botspot.trade/mcp"
bearer_token_env_var = "BOTSPOT_API_KEY"CLI setup
Gemini CLI
- Best for
- Using Gemini CLI with the same BotSpot strategies, broker context, backtests, and trading workflows.
- Authentication
- OAuth
- Add BotSpotRun the command below to add the hosted BotSpot MCP server.
- AuthorizeLet Gemini CLI discover BotSpot OAuth, then complete the browser login when prompted. Use
/mcp auth botspotif authentication is still required. - Confirm the connectionRun
gemini mcp listand check that BotSpot is connected.
gemini mcp add --transport http botspot https://mcp.botspot.trade/mcpIDE setup
Cursor
- Best for
- Bringing BotSpot strategy context into a code editor without copying credentials into prompts.
- Authentication
- BotSpot API key
- Choose scopeUse
.cursor/mcp.jsonfor one project or~/.cursor/mcp.jsonglobally. - Add BotSpotPaste the config below and replace the placeholder with a BotSpot API key.
{
"mcpServers": {
"botspot": {
"url": "https://mcp.botspot.trade/mcp",
"headers": {
"Authorization": "Bearer botspot_YOUR_API_KEY"
}
}
}
}