Guide for JetBrains AI Assistant
Integrate JetBrains AI Assistant with AI Architect for more accurate, codebase-aware AI assistance.
Use Bito's AI Architect with JetBrains AI Assistant to enhance your AI-powered coding experience.
Once connected via MCP (Model Context Protocol), JetBrains AI Assistant can leverage AI Architectβs deep contextual understanding of your project, enabling more accurate code suggestions, explanations, and code insights.
Prerequisites
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.
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.
JetBrains IDE: IntelliJ IDEA 2025.1+ (or PyCharm, WebStorm, PhpStorm, etc. 2025.1+)
AI Assistant Plugin (version 251.26094.80.5 or higher)
Open your JetBrains IDE
Go to: Settings (Ctrl/Cmd + Alt + S)
Navigate to: Plugins
Search for "AI Assistant"
Verify version is 251.26094.80.5 or higher
Node.js: 20.18.1+ installed (for mcp-remote proxy)
Why Node.js 20+? The mcp-remote proxy depends on undici v7, which requires Node.js 20+ (needs the
Fileglobal API added in Node 20.0.0). Node.js 18 and earlier will fail withReferenceError: File is not defined.Verify:
node --version # Should show v20.x.x or higher npx --versionIf Node.js is not installed or the version < 20 then download Node.js 20.x LTS
Set up AI Architect
JetBrains AI Assistant has the same setup process across all platforms (Windows, macOS, Linux, WSL).
Configure BitoAIArchitect
BitoAIArchitectmacOS/Linux configuration:
Fill in the fields as follows:
Name:
BitoAIArchitectCommand:
npxArgs (add each on a separate line by clicking the + button):
-ymcp-remote<Your-Bito-MCP-URL>--headerAuthorization:${AUTH_HEADER}
Environment Variables (click + to add):
Key:
AUTH_HEADERValue:
Bearer <Your-Bito-MCP-Access-Token>
Windows configuration (IMPORTANT - uses cmd):
Fill in the fields as follows:
Name:
BitoAIArchitectCommand:
cmdArgs (add each on a separate line):
/cnpx-ymcp-remote<Your-Bito-MCP-URL>--headerAuthorization:${AUTH_HEADER}
Environment Variables:
Key:
AUTH_HEADERValue:
Bearer <Your-Bito-MCP-Access-Token>
Add guidelines (optional but highly recommended)
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 rules to a specific project:
Navigate to your project root
Create
.aiassistant/rules/directory:Create a rule file (e.g.,
bitoai-architect.md):Copy the contents of your BitoAIArchitectGuidelines.md file into
.aiassistant/rules/bitoai-architect.mdfile:In your IDE: Settings β Tools β AI Assistant β Rules
The rule file should appear automatically
Configure how it should be applied:
Always: Applied to all chats automatically
Manually: Invoked using
@rule:bitoai-architectBy Model Decision: AI decides when to apply
By File Patterns: Applied when specific files are open
What AI Assistant rules should contain:
BitoAIArchitectMCP usage instructionsWhen to query organizational repositories
How to search for dependencies and tech stacks
Troubleshooting
JetBrains AI Assistant not showing MCP settings:
Verify IDE version is 2025.1 or later
Verify AI Assistant plugin is version 251.26094.80.5+
Update both if needed
BitoAIArchitect not appearing or showing "Not started":
BitoAIArchitect not appearing or showing "Not started":Verify Node.js is installed:
node --versionCheck that you've toggled "Codebase" mode ON in the chat
On Windows, ensure you're using
cmdcommand (notnpxdirectly)Restart the IDE completely
Check IDE logs for errors: Help β Show Log in Explorer/Finder
Look for files in the
mcpfolder
Connection errors:
Test the endpoint manually:
Verify your Bito MCP URL and Bito MCP Access Token are correct
Check firewall settings
Verify the
--headerargument format:Authorization:${AUTH_HEADER}(colon, no space)
Windows-specific issues:
Verify you're using
cmdas the command (notnpx)Ensure
/cis the first argumentNode.js must be in system PATH
Last updated

