Skip to content
BuildBase
BuildBase in your AI tools

Use BuildBase in Junie

BuildBase in your AI tools: connect Junie to BuildBase's own MCP server and manage your BuildBase organization from Junie. You sign in as yourself, and Junie can do only what your role and your organization allow.

Add BuildBase to Junie

The address is the same in every AI tool: https://api.console.buildbase.app/mcp. BuildBase signs you in the first time Junie connects.

  1. In Junie, add a remote MCP server: .junie/mcp/mcp.json or ~/.junie/mcp/mcp.json. Use the address https://api.console.buildbase.app/mcp, or the command or config below.
  2. Sign in. The server shows Authorization required. Run /mcp, choose it, then Authorize, and sign in in the browser; it turns Active.
  3. On BuildBase's sign-in page, sign in as you do to the console, then approve the consent screen, which names Junie and what it asks for.
  4. Ask Junie something, such as "List my BuildBase organizations."
.junie/mcp/mcp.jsonJSON
{
  "mcpServers": {
    "buildbase-console": {
      "url": "https://api.console.buildbase.app/mcp"
    }
  }
}

The plan it needs

JetBrains' Junie MCP page does not name a plan.

How sign-in looks in Junie

The server shows Authorization required. Run /mcp, choose it, then Authorize, and sign in in the browser; it turns Active.

What is different in Junie

  • Junie's MCP page does not document per-tool controls.
  • BuildBase adds its own rules on top: each organization is Off, Read only or Read and change for AI agents (Read only by default), and deletes, member and role changes, sends and money moves need your approval in the chat.
  • For a job with nobody to sign in, send one of your organization's API keys as the bearer instead. Add headers, with Authorization: Bearer <key>, next to url in mcp.json.
  • The Junie CLI and the Junie plugin in JetBrains IDEs share one configuration: .junie/mcp/mcp.json in a project, ~/.junie/mcp/mcp.json for every project.

If it does not work in Junie

Junie needs to sign in again
Run /mcp, choose the server, then Reconnect or Authorize.
Junie does not connect
A server marked Failed or Inactive: /mcp > Reconnect, or raise its timeout (milliseconds, 60 seconds by default).
Junie says the organization does not let agents in
An owner or admin sets the organization's AI agents setting in the console, under Account, then Security. Off turns every agent away, and an owner or admin can also block one agent for one member there.
Junie cannot change anything
The organization is Read only, the default. An owner or admin can switch it to Read and change, and Junie can then make changes without signing in again. Deleting, sending to an audience, roles and money still ask you to approve each change.

Frequently Asked Questions

Which Junie plan do I need?

JetBrains' Junie MCP page does not name a plan.

Can Junie change things in my BuildBase organization?

Only where the organization allows it: Read only is the default. Even then, deletes, member and role changes, sends and money moves need your approval in the chat, and secrets never reach Junie.

Can I connect Junie with an API key instead of signing in?

Yes, for a job with nobody to sign in: send one of your organization's API keys as the bearer. Add headers, with Authorization: Bearer <key>, next to url in mcp.json. The key works in its own organization only, and the organization's AI agents setting still applies.

Where next