@optimalai/optibot-mcp

v1.1.0

Published

3 days ago

MCP server for AI code reviews powered by Optibot

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.

What It Does

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:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "optibot": {
      "command": "npx",
      "args": ["-y", "@optimalai/optibot-mcp"],
      "env": {
        "OPTIBOT_API_KEY": "optk_your_key_here"
      }
    }
  }
}

Cursor

Add to your Cursor MCP configuration:

Global (all projects): ~/.cursor/mcp.json
Project-level: .cursor/mcp.json in your project root

{
  "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 -e OPTIBOT_API_KEY=optk_your_key_here -- npx -y @optimalai/optibot-mcp

The -e flag stores the API key in the MCP server config so it is always available when Claude Code spawns the server, regardless of your shell environment.

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).

Usage

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 |

Real-Time Progress

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:

started — Review request accepted
analyzing_patch — Parsing and analyzing the diff
tool_call — Running analysis tools (with tool name and query details)
generating_review — Generating the final review
completed — Review finished

CI/CD Integration

For automated reviews in CI/CD pipelines (GitHub Actions, GitLab CI, etc.), use the Optibot CLI instead. The CLI is purpose-built for non-interactive environments and runs as a standard command-line tool.

The MCP server is designed to run inside AI assistants (Claude Desktop, Cursor, etc.) — it speaks the MCP stdio protocol and is not intended to be invoked directly in a pipeline.

To use in CI:

Generate an API key from the Optibot dashboard or with create_api_key tool
Add OPTIBOT_API_KEY as a repository secret
Use the CLI in your pipeline:

# GitHub Actions
- name: Install Optibot CLI
  run: npm install -g @optimalai/optibot
- name: Run code review
  env:
    OPTIBOT_API_KEY: ${{ secrets.OPTIBOT_API_KEY }}
  run: optibot review --branch origin/${{ github.base_ref }}

See the Optibot CLI README for full CI/CD setup instructions including GitLab CI.

Environment Variables

| Variable | Description | |----------|-------------| | OPTIBOT_API_KEY | Your API token (required for automated use) | | OPTIBOT_API_URL | Custom backend URL (must use https://, defaults to https://agents.getoptimal.ai) |

Published

Vulnerabilities

Links

Maintainers

Keywords

Readme