Connect JetBrains Air to Busabase
JetBrains' system for building software with agents. Air in IDEs runs coding agents such as Claude Agent, Codex, Gemini CLI, Junie and GitHub Copilot — plus any agent connected via the Agent Client Protocol (ACP) — side by side, with every change reviewable in context. Air Teams runs shared projects and automations in dedicated cloud environments, and Air Governance controls which agents, models and MCP servers an organization uses.
Paste this into JetBrains Air
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

Give your agent this one instruction
You end up with more than a connector: the busabase skill carries the whole change-request 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
Skills belong to the agent Air is running, not to Air itself: install the Busabase skill separately for each agent you use in Air (Claude Agent, Codex, Gemini CLI, Junie, Copilot). Air automations can also carry startup scripts, MCP servers and skills for the run, but the skill is still loaded by the underlying agent.
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 + API key · Plugin / Skill
- Transport
- Streamable HTTP
- Authentication
- API key
- Config file
- .mcp.json (repository root, cloud tasks and automations)
Air runs other coding agents, and each of those agents can execute shell commands and fetch URLs, so the Skill path applies to the agent itself: start the agent in Air and ask it to Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. The agent installs the Busabase skill in its own usual location, and later Air sessions with that agent can use it.
Give every cloud task and automation the Busabase connector
For Air Teams cloud tasks and automations, add Busabase as an MCP server in a .mcp.json file at the repository root:
{
"mcpServers": {
"busabase": {
"url": "https://busabase.com/api/mcp",
"headers": {
"Authorization": "Bearer ${BUSABASE_API_KEY}"
}
}
}
}
Add the API key's value as a secret named BUSABASE_API_KEY in the environment configuration (names are case-sensitive) — never write the token into the file itself. Commit and push; the next cloud task or automation run on that branch gets the server. The Air app also configures MCP servers through its own settings (see the vendor's MCP page linked below).
JetBrains Air MCP documentation
Known gotchas
Busabase is not on Air Teams' managed connector list (Confluence, Figma, GitHub, GitLab, Grafana, Jira, Linear, Sentry, TeamCity, YouTrack), so the `.mcp.json` route above is the way in; the connector list's sign-in flow does not apply to custom servers, and the vendor docs describe header-token auth for `.mcp.json` servers rather than OAuth, so auth-mode is api-key. If a managed connector and a `.mcp.json` entry share a name, the agent gets the connector and the `.mcp.json` entry is skipped. Project-level connectors do not reach cloud tasks — cloud tasks only use personal connectors.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | |||
|---|---|---|---|
| Type | AI editors | Terminal agents | AI editors |
| Recommended path | Agent Skill | Agent Skill | Agent Skill |
| How it connects | MCP + API key · Plugin / Skill | MCP + OAuth · Plugin / Skill | MCP + OAuth · Plugin / Skill |
| Transport | Streamable HTTP | Streamable HTTP | Streamable HTTP |
| Authentication | API key | OAuth (dynamic registration) | OAuth (dynamic registration) |
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.
Let your agent do the setup
One instruction, one authorization, and every change it makes afterwards carries a message and a diff you can check or revert.
Browse every agentPaste this into JetBrains Air
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.