Guide for Junie (JetBrains)

Integrate Junie (JetBrains) with AI Architect for more accurate, codebase-aware AI assistance.

Use Bito's AI Architect with Junie (JetBrains) to enhance your AI-powered coding experience.

Once connected via MCP (Model Context Protocol), Junie can leverage AI Architect’s deep contextual understanding of your project, enabling more accurate code suggestions, explanations, and code insights.

Prerequisites

  1. Follow the AI Architect installation instructions. Upon successful setup, you will receive a Bito MCP URL and Bito MCP Access Token that you need to enter in your coding agent.

  2. Download BitoAIArchitectGuidelines.md file. You will need to copy/paste the content from this file later when configuring AI Architect.

    • Note: This file contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server. The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

  3. Junie installed in a JetBrains IDE (IntelliJ IDEA, PyCharm, WebStorm, etc.)

  4. Node.js 20.18.1+ installed (for mcp-remote proxy)

    1. Why Node.js 20+? The mcp-remote proxy depends on undici v7, which requires Node.js 20+ (needs the File global API added in Node 20.0.0). Node.js 18 and earlier will fail with ReferenceError: File is not defined.

    2. Verify:

      node --version  # Should show v20.x.x or higher
      npx --version
    3. If Node.js is not installed or the version < 20 then download Node.js 20.x LTS

Set up AI Architect

Junie has the same setup process across all platforms (Windows, macOS, Linux, WSL).

1

Access Junie MCP settings

  1. Open your JetBrains IDE (IntelliJ, PyCharm, etc.)

  2. Go to: Settings (Ctrl/Cmd + Alt + S)

  3. Navigate to: Tools β†’ Junie β†’ MCP Settings

  4. Click the + (Add) button to open the global mcp.json configuration file in the editor, or manually edit the file as shown below

2

Configure BitoAIArchitect

The global configuration file is located at:

  • macOS/Linux: ~/.junie/mcp/mcp.json

  • Windows: %USERPROFILE%\.junie\mcp\mcp.json

macOS/Linux configuration:

Windows configuration (IMPORTANT - uses cmd /c):

Note:

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

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

3

Save and restart

  1. Save the mcp.json file

  2. Close all JetBrains IDE windows

  3. Reopen your IDE

4

Verify connection

  1. Go to: Settings β†’ Tools β†’ Junie β†’ MCP Settings

  2. Check that BitoAIArchitect appears in the server list

  3. Status should show as Connected or Running

5

The BitoAIArchitectGuidelines.md file contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server.

The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

To add Bito AI Architect usage guidelines to a specific project:

  1. Navigate to your project root

  2. Create .junie directory:

    Copy the contents of your BitoAIArchitectGuidelines.md file into .junie/guidelines.md file:

  3. Junie will automatically use these guidelines for the project

What Junie guidelines should contain:

  • BitoAIArchitect MCP usage best practices

  • When to query repository information

  • How to search for dependencies and tech stacks

Troubleshooting

Junie not showing BitoAIArchitect:

  1. Verify Node.js is installed: node --version

  2. Check mcp.json syntax (must be valid JSON)

  3. On Windows, ensure you're using cmd with /c argument

  4. Restart the IDE completely

Connection errors:

  1. Test the endpoint manually:

Note:

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

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

  1. Verify your Bito MCP URL and Bito MCP Access Token are correct

  2. Check firewall settings

Last updated