Home Optibot for IDE
🖥️

Optibot for IDE

Using Optibot with your IDE environment on cursor, windsurf, antigravity, vscode and others.
By Optimal Engineering
2 articles

Optibot MCP

Optibot MCP Server — AI Code Reviews for Any Editor An MCP server that brings Optibot AI-powered code reviews to Claude Desktop, Cursor, Windsurf, Claude Code, and any MCP-compatible client. Review local changes, compare branches, and get actionable feedback — all from your AI assistant. What is MCP? The Model Context Protocol is an open standard that lets AI assistants use external tools and data sources. Once you add this server, your assistant can run Optibot reviews on your behalf — just ask in natural language. How it works - Review your code — say "review my changes" and get an AI code review instantly - Compare branches — "review my branch against main" triggers a full branch diff review - Review patch files — point it at any .patch or .diff file - Manage API keys — create, list, and delete keys for CI/CD automation - Detect merge conflicts — warns you about conflicts before you review Install npm install -g @optimalai/optibot-mcp Setup Claude Desktop Add to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json on macOS): { "mcpServers": { "optibot": { "command": "npx", "args": ["-y", "@optimalai/optibot-mcp"], "env": { "OPTIBOT_API_KEY": "optk_your_key_here" } } } } Cursor Add to your Cursor MCP configuration (.cursor/mcp.json): { "mcpServers": { "optibot": { "command": "npx", "args": ["-y", "@optimalai/optibot-mcp"], "env": { "OPTIBOT_API_KEY": "optk_your_key_here" } } } } Windsurf Add to your Windsurf MCP configuration (~/.codeium/windsurf/mcp_config.json): { "mcpServers": { "optibot": { "command": "npx", "args": ["-y", "@optimalai/optibot-mcp"], "env": { "OPTIBOT_API_KEY": "optk_your_key_here" } } } } Claude Code claude mcp add optibot -- npx -y @optimalai/optibot-mcp Then set your API key as an environment variable: export OPTIBOT_API_KEY=optk_your_key_here Authentication Option 1: API Key (Recommended for MCP) Set the OPTIBOT_API_KEY environment variable in your MCP client configuration. You can generate a key from the Optibot dashboard or using the CLI: npx @optimalai/optibot apikey create my-mcp-key Option 2: Browser Login Use the login tool to authenticate via browser. This saves credentials to ~/.optibot/config.json (90-day token). How to use Optibot with the MCP Once configured, just ask your AI assistant naturally: What you say | What happens review my changes | Reviews uncommitted local changes review my branch against main | Compares current branch against main review this diff file | Reviews an arbitrary patch file check if I'm authenticated | Shows current auth status create an API key for CI | Creates and displays a new API key list my API keys | Lists all API keys with metadata Available Tools Tool | Description `review_local_changes` | Review uncommitted local changes (git diff HEAD) `review_branch` | Review changes against a target branch (auto-detects or specify) `review_diff_file` | Review an arbitrary diff/patch file login | Authenticate via browser OAuth logout | Remove saved credentials check_auth | Check current authentication status create_api_key | Create a new API key for CI/CD list_api_keys | List all API keys delete_api_key | Delete an API key by ID get_profile | Get your user profile and review quota status

Last updated on Mar 17, 2026

Reviewing code with Optibot MCP

Watch review progress in real time During reviews, the MCP server connects to the Optibot backend via WebSocket and emits real-time progress notifications using MCP logging messages. Your MCP client will receive updates as the review progresses through these steps: 1. started — Review request accepted 2. analyzing_patch — Parsing and analyzing the diff 3. tool_call — Running analysis tools (with tool name and query details) 4. generating_review — Generating the final review 5. completed — Review finished CI/CD Integration The Optibot MCP server can be used in CI/CD pipelines for automated code reviews. Use the OPTIBOT_API_KEY environment variable for headless (non-interactive) authentication — no browser login is needed. Setting Up 1. Generate an API key from the Optibot dashboard or using the create_api_key tool. 2. Store it as a secret in your CI provider (e.g., GitHub Actions secret, GitLab CI variable). 3. Pass it as OPTIBOT_API_KEY in your pipeline environment. GitHub Actions Example - name: Optibot Review env: OPTIBOT_API_KEY: ${{ secrets.OPTIBOT_API_KEY }} run: npx @optimalai/optibot-mcp Other CI Providers Set the OPTIBOT_API_KEY environment variable in your pipeline configuration. The MCP server will automatically use it for authentication without requiring interactive login. Environment Variables VariableDescriptionOPTIBOT_API_KEYYour API token (required for automated use)OPTIBOT_API_URLCustom backend URL (defaults to https://agents.getoptimal.ai)

Last updated on Mar 17, 2026