BotSpot MCP Integration

Use BotSpot MCP when you want your AI assistant to create and edit LumiBot strategies, run hosted historical backtests, inspect results, and report on your existing bots. A paid BotSpot plan is required; data access and usage limits depend on your plan and the requested workflow.

Start with the maintained setup guide. It contains current Claude Code, Cursor, Codex and hosted-client instructions, first-use prompts, pricing and connection troubleshooting.

Connect and try one workflow

1. Add the Streamable HTTP endpoint https://mcp.botspot.trade/mcp in your client.

2. Complete the client’s normal BotSpot OAuth sign-in.

3. Ask the assistant to check account access, create a strategy, run a historical backtest, and inspect that exact run using the starter prompts.

Strategy creation uses create_strategy followed by the saved-file and revision tools. Every edit creates a new revision; start a backtest from the newest saved revision. Keep the returned backtest ID for status, chart and artifact requests. A queued backtest is not a completed result.

No brokerage connection is needed for the starter historical example when your plan includes its required data. Backtests are simulations and do not guarantee future returns.

Permissions and availability

The direct MCP connection includes trading and deployment actions, subject to account permissions, plan entitlements and normal product approvals. An account connection alone does not authorize a trade. Protect API keys; never paste them into a chat or commit them to source control.

Custom MCP installation and public app-store approval are separate. The planned restricted store connection is still awaiting qualification and release. Check the distribution tracker for submitted, approved and installation-tested destinations.

To disconnect, use your client’s connector controls. Revoke any separate BotSpot API key through BotSpot Account Settings.