Busabase for Junie

Connect Junie to Busabase

JetBrains coding agent available in the terminal, JetBrains IDEs, and headless CI/CD workflows.

Paste this into Junie

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

Read the Junie documentation

Busabase

Agent Skill

Give your agent this one instruction

You end up with more than a connector: the busabase skill carries the whole approval-first workflow, the CLI, and the full API — available in every future session without re-pasting anything.

Asks first

Busabase Cloud or Personal Desktop — your call, before anything happens.

Connects

Signs you in and stores the credential itself. No API key to copy by hand.

Seeds a Base

Creates and fills your first Base, so the workspace is not an empty screen.

Installs the skills

busabase and busabase-app-creator become permanent, for every session after this.

For this agent

Use Junie CLI in the target repository so it can install project-scoped skills and run the setup commands with your approval.

Prefer a connector?

If you would rather wire Busabase in as MCP tools than let the agent install a skill, use the server URL below.

At a glance

Vendor: JetBrains
How it connects: MCP + OAuth · Plugin / Skill · busabase-cli · REST API
Transport: Streamable HTTP
Authentication: Unknown
Config file: ~/.junie/mcp/mcp.json or .junie/mcp/mcp.json

Run this

curl -fsSL https://junie.jetbrains.com/install.sh | bash

Install Junie CLI, run junie in a trusted project, and ask: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Review each requested action, complete authentication, and ask Junie to verify the active Busabase workspace and installed skills.

Known gotchas

Junie documents browser-assisted OAuth for remote MCP servers but does not state the client registration mode. User-level MCP configuration overrides project entries with the same server name.

These stepsFrom official docsNo check date recorded

Written from this agent's own documentation. We have not re-run every step on a real machine, so check the linked docs if a command has changed.

Where these steps come from Official site

Let your agent do the setup

One instruction, reviewed access, and every change it makes afterwards arrives as a proposal you approve.

Browse every agent

Paste this into Junie

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

All agents

Busabase for Junie

Connect Junie to Busabase

JetBrains coding agent available in the terminal, JetBrains IDEs, and headless CI/CD workflows.

Paste this into Junie

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

Read the Junie documentation

Busabase

Agent Skill

Give your agent this one instruction

You end up with more than a connector: the busabase skill carries the whole approval-first workflow, the CLI, and the full API — available in every future session without re-pasting anything.

Asks first

Busabase Cloud or Personal Desktop — your call, before anything happens.

Connects

Signs you in and stores the credential itself. No API key to copy by hand.

Seeds a Base

Creates and fills your first Base, so the workspace is not an empty screen.

Installs the skills

busabase and busabase-app-creator become permanent, for every session after this.

For this agent

Use Junie CLI in the target repository so it can install project-scoped skills and run the setup commands with your approval.

Prefer a connector?

If you would rather wire Busabase in as MCP tools than let the agent install a skill, use the server URL below.

At a glance

Vendor: JetBrains
How it connects: MCP + OAuth · Plugin / Skill · busabase-cli · REST API
Transport: Streamable HTTP
Authentication: Unknown
Config file: ~/.junie/mcp/mcp.json or .junie/mcp/mcp.json

Run this

curl -fsSL https://junie.jetbrains.com/install.sh | bash

Known gotchas

Junie documents browser-assisted OAuth for remote MCP servers but does not state the client registration mode. User-level MCP configuration overrides project entries with the same server name.

These stepsFrom official docsNo check date recorded

Written from this agent's own documentation. We have not re-run every step on a real machine, so check the linked docs if a command has changed.

Where these steps come from Official site

Let your agent do the setup

One instruction, reviewed access, and every change it makes afterwards arrives as a proposal you approve.

Browse every agent

Paste this into Junie

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

All agents

Busabase for Junie

Connect Junie to Busabase

JetBrains coding agent available in the terminal, JetBrains IDEs, and headless CI/CD workflows.

Paste this into Junie

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

Read the Junie documentation

Busabase

Agent Skill

Give your agent this one instruction

You end up with more than a connector: the busabase skill carries the whole approval-first workflow, the CLI, and the full API — available in every future session without re-pasting anything.

Asks first

Busabase Cloud or Personal Desktop — your call, before anything happens.

Connects

Signs you in and stores the credential itself. No API key to copy by hand.

Seeds a Base

Creates and fills your first Base, so the workspace is not an empty screen.

Installs the skills

busabase and busabase-app-creator become permanent, for every session after this.

For this agent

Use Junie CLI in the target repository so it can install project-scoped skills and run the setup commands with your approval.

Prefer a connector?

If you would rather wire Busabase in as MCP tools than let the agent install a skill, use the server URL below.

At a glance

Vendor: JetBrains
How it connects: MCP + OAuth · Plugin / Skill · busabase-cli · REST API
Transport: Streamable HTTP
Authentication: Unknown
Config file: ~/.junie/mcp/mcp.json or .junie/mcp/mcp.json

Run this

curl -fsSL https://junie.jetbrains.com/install.sh | bash

Known gotchas

Junie documents browser-assisted OAuth for remote MCP servers but does not state the client registration mode. User-level MCP configuration overrides project entries with the same server name.

These stepsFrom official docsNo check date recorded

Written from this agent's own documentation. We have not re-run every step on a real machine, so check the linked docs if a command has changed.

Where these steps come from Official site

Let your agent do the setup

One instruction, reviewed access, and every change it makes afterwards arrives as a proposal you approve.

Browse every agent

Paste this into Junie

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.