Quick MCP integration with AI coding agents

Connect Bito's AI Architect to your AI coding tools (Cursor, Claude Code, Windsurf, etc.) in seconds with our automated installer

Prerequisites

Before running the installer, have these ready:

1. Set up AI Architect — AI Architect can be set up using one of the following deployment options:

   1. Bito-hosted (Fully managed by Bito — no infrastructure setup required)

   2. Self-hosted (Run AI Architect on your own infrastructure for maximum control)

2. Your Bito Workspace ID or full Bito MCP URL

   1. You can find your Bito MCP URL on the AI Architect settings > MCP settings page.

   2. You can find your Bito Workspace ID on the Workspace settings page.

3. Your Bito MCP Access Token — optional. If omitted, the installer configures the MCP client to complete SSO/OAuth against the server on first use. Most modern IDE MCP clients (Claude Code, Cursor, Windsurf, VS Code, Junie, JetBrains via mcp-remote) support this. Bito MCP advertises OAuth 2.1 discovery (PKCE, Dynamic Client Registration) at https://mcp.bito.ai/{workspace}/.well-known/oauth-authorization-server.

Note: For self-hosted instances, follow the self-hosted AI Architect installation instructions. Upon successful setup, you will receive a Bito MCP URL and Bito MCP Access Token that you need to enter.

1. Your email ID (for tracking/identification)

2. At least one supported tool installed:

   • Claude Code

   • Cursor

   • Windsurf

   • VS Code (GitHub Copilot)

   • GitHub Copilot CLI

   • Junie

   • Google Antigravity (IDE + agy CLI)

   • JetBrains AI Assistant

   • OpenAI Codex CLI

Note: For Claude.ai (Web) , Claude Desktop, and ChatGPT (Web & Desktop) you'll need to follow the manual setup process as they require OAuth authentication through your web browser.

Installation guide

Our automated installer will prompt you for credentials and automatically configure all supported AI tools available on your system.

macOS / Linux

Open your terminal and run:

curl -fsSL https://mcp-setup.bito.ai/install.sh | bash

Windows

Run in PowerShell (not Command Prompt).

1. One-time PowerShell setup (first time only):

By default, PowerShell blocks scripts from running. Run this once to allow signed scripts to execute:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

Per-user, no admin required.

2. Run the installer:

irm https://mcp-setup.bito.ai/install.ps1 | iex

The script will prompt you for credentials and automatically configure all detected IDEs.

Note: When using a self-hosted AI Architect, ensure that the MCP server is up and running before proceeding with the setup. The setup will fail if MCP is not running.

What happens next

1. The installer downloads the necessary files and checks for compatible tools

2. You'll be prompted to enter your credentials

   • Refer to the Prerequisites section for more details.

3. Automatic configuration - All detected tools are configured

4. Agent skills installed - Agent skills are downloaded and installed for your configured tools

Learn more about available Agent skills.

Note: Agent skills auto-sync daily (and on every Claude Code session start)

1. Guidelines configured - Bito's AI Architect guidelines file is automatically configured globally on Claude Code and Windsurf. To apply guidelines at the project level, see the Add guidelines section below.

2. Confirmation - You'll see which tools were successfully set up

After installation

1

Restart your AI tool

After the installer completes, completely close and reopen your IDE(s) to ensure the configuration takes effect.

2

Verify AI architect connection

Check that AI Architect appears in your tool's MCP server list:

• Claude Code: Run claude mcp list

• GitHub Copilot CLI: Run copilot mcp list (or /mcp in a copilot session)

• OpenAI Codex CLI: Run codex mcp list (or /mcp in a codex session)

• Cursor: Settings → MCP → Check server list

• Windsurf: Settings → Cascade → MCP Servers

• VS Code: Copilot Chat → Tools icon

• Junie: Settings → Tools → Junie → MCP Settings

• Antigravity (IDE + agy CLI): Click "..." menu > MCP Servers > View raw config, or run /mcp in agy

• JetBrains AI Assistant: Settings → Tools → AI Assistant → Model Context Protocol

3

Add guidelines (optional but highly recommended)

The BitoAIArchitectGuidelines.md file contains best practices, usage instructions, and prompting guidelines for the Bito's AI Architect MCP server. Adding it to your project helps your AI coding agent interact with Bito's AI Architect more effectively and get better results out of every query.

If you are on Claude Code or Windsurf, the installer automatically adds the guidelines file globally, covering all your projects. If you'd also like to apply guidelines at the project level for a specific project, run the relevant command below inside that project directory.

If you are on Cursor, VS Code (GitHub Copilot), Junie, or JetBrains AI Assistant, guidelines are not configured automatically by the installer. Run the relevant command below manually inside each project directory where you want the guidelines to apply. This is a per-project step, so repeat it whenever you start working in a new project.

To add Bito's AI Architect guidelines to your project, run the following commands based on your coding agent:

Claude Code:

cd /path/to/your/project
curl -sSL "https://mcp-setup.bito.ai/BitoAIArchitectGuidelines.md" -o CLAUDE.md

Cursor:

cd /path/to/your/project
curl -sfL "https://mcp-setup.bito.ai/BitoAIArchitectGuidelines.md" -o .cursorrules

Windsurf:

cd /path/to/your/project
mkdir -p .windsurf/rules
curl -sfL "https://mcp-setup.bito.ai/BitoAIArchitectGuidelines.md" -o .windsurf/rules/bitoai-architect.md

VS Code (GitHub Copilot):

cd /path/to/your/project
mkdir -p .github
curl -sfL "https://mcp-setup.bito.ai/BitoAIArchitectGuidelines.md" -o .github/copilot-instructions.md

Junie:

cd /path/to/your/project
mkdir -p .junie
curl -sfL "https://mcp-setup.bito.ai/BitoAIArchitectGuidelines.md" -o .junie/guidelines.md

JetBrains AI Assistant:

cd /path/to/your/project
mkdir -p .aiassistant/rules
curl -sfL "https://mcp-setup.bito.ai/BitoAIArchitectGuidelines.md" -o .aiassistant/rules/bitoai-architect.md

Note: guidelines file auto-sync daily (and on every Claude Code session start)

4

Run a test query

Open a chat or conversation in your AI tool and try a test query to confirm AI Architect is working:

• "What repositories are available in my organization?"

• "Show me all Python repositories"

• "List the available tools"

• "What are the dependencies of [repo-name]?"

• "Find all microservices using Redis"

• "Show me repository clusters in our organization"

• "Plan a new feature for [component]"

  • (uses bito-feature-plan skill)

• "Write a PRD for [feature]"

  • (uses bito-prd skill)

• "Help me triage this production issue"

  • (uses bito-production-triage skill)

If you receive accurate responses about your codebase, the setup is complete!

Learn more about available Agent skills.

Note: Agent skills auto-sync daily (and on every Claude Code session start)

Uninstalling

To remove Bito AI Architect from all tools:

macOS / Linux

Open your terminal and run:

curl -fsSL https://mcp-setup.bito.ai/uninstall.sh | bash

Windows

Run in PowerShell (not Command Prompt).

If you haven't already done so during install, run this once to allow signed scripts:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

After that run the following command:

irm https://mcp-setup.bito.ai/uninstall.ps1 | iex

Need manual setup?

If you prefer to configure tools individually or need to set up web-based tools (Claude.ai, ChatGPT), refer to our detailed integration guides:

• Claude Code

• Claude Desktop

• Claude.ai (Web)

• Cursor

• Windsurf

• GitHub Copilot (VS Code)

• Junie

• JetBrains AI Assistant

• ChatGPT (Web & Desktop)

Troubleshooting

Installer issues

"Command not found" or similar errors:

• Verify you're using the correct shell (bash for macOS/Linux, PowerShell for Windows)

• Check your internet connection

• Try running the command again

No tools detected:

• Ensure your AI tools are installed before running the installer

• The installer only configures tools it can detect on your system

• You can run the installer again after installing new tools

Connection issues

• Verify Bito MCP URL and Bito MCP Access Token are correct.

• Test endpoint with MCP protocol:

curl -s -X POST \
  -H "Authorization: Bearer <Your-Bito-MCP-Access-Token>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"initialize","params":{},"id":1}' \
  <Your-Bito-MCP-URL>

# Should return HTTP 200 with JSON response for valid credentials
# HTTP 401: Invalid Bito MCP Access Token
# HTTP 404: Invalid Bito MCP URL

Note:

• Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

  • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

    Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at alpha.bito.ai

• Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

Server not appearing after install:

• Completely restart your AI tool (don't just reload)

• Verify your credentials were entered correctly

• Check that you have the minimum required versions (see below)

Minimum requirements

Some tools require specific versions:

• Node.js 20.18.1+ for Claude Desktop, VS Code, and JetBrains

• VS Code 1.99+ with Agent Mode enabled

• JetBrains 2025.1+ with AI Assistant plugin 251.26094.80.5+

Check Node.js version:

node --version

If you need to install or update Node.js, visit nodejs.org

Skills not appearing

If skills are not visible in your IDE after installation:

1. Verify files exist: ls ~/.claude/skills/bito-*/SKILL.md (Claude) or ls ~/.cursor/rules/bito-*.mdc (Cursor)

2. Restart your IDE completely

3. Check that jq is installed (required for manifest parsing): jq --version

4. Re-run the install script — skills installation is idempotent

Hooks not working

If hooks are not triggering:

1. Verify your IDE version supports hooks (Cursor hooks are in beta, VS Code hooks are preview)

2. Check that the hook configuration wasn't overwritten by another tool

3. Re-run the install script to restore hook configuration