Busabase for Amazon Q Developer

Connect Amazon Q Developer to Busabase

AWS's generative-AI assistant for building and operating AWS applications — available as a terminal CLI and as an extension for VS Code, JetBrains, Visual Studio and Eclipse.

Paste this into Amazon Q Developer

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 Amazon Q Developer 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 the CLI (`q chat`) for the Skill path — it has the shell access the setup document needs. The IDE extension is chat-oriented and better suited to the connector route below.

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: AWS
How it connects: Plugin / Skill · MCP + OAuth
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)
Config file: ~/.aws/amazonq/cli-agents (IDE: ~/.aws/amazonq/agents/default.json)

Run this

qchat mcp add --name busabase --url https://busabase.com/api/mcp

Amazon Q Developer has a terminal-based CLI (q chat / qchat), so the Skill path applies — hand it the prompt above.

Prefer a connector?

AWS's docs state that the CLI "supports both local MCP servers (that run as processes) and remote MCP servers (that communicate over HTTP). Remote servers can use OAuth authentication or be open (no authentication required)."

CLI — remote servers are configured in your agent configuration file with the type and url fields:

{
  "mcpServers": {
    "busabase": {
      "type": "http",
      "url": "https://busabase.com/api/mcp"
    }
  }
}

Global CLI agent config lives at ~/.aws/amazonq/cli-agents. Manage servers with qchat mcp add | remove | list | import | status.

For OAuth, AWS documents this flow: start the session with an agent that includes the server (it shows as "not yet loaded"), run /mcp to begin authentication, open the URL it prints while keeping the Q CLI session open, finish in the browser, then return — the server's tools become available once authentication completes.

IDE — global config is ~/.aws/amazonq/agents/default.json. In the UI, select http as the transport protocol, put the server URL in the URL field, and optionally add key-value pairs under Headers. If the endpoint requires authorization, Amazon Q automatically opens a browser page for you to authorize it.

Using MCP with Amazon Q Developer · CLI MCP configuration · IDE MCP configuration

Known gotchas

CLI and IDE read different config files (`~/.aws/amazonq/cli-agents` vs `~/.aws/amazonq/agents/default.json`) — configuring one does not configure the other. Remote servers need `"type": "http"` alongside `url`; omitting `type` leaves it treated as a local stdio entry. During OAuth, keep the Q CLI session open while you complete the browser flow, or the handshake will not complete.

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 Amazon Q Developer

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 Amazon Q Developer

Connect Amazon Q Developer to Busabase

AWS's generative-AI assistant for building and operating AWS applications — available as a terminal CLI and as an extension for VS Code, JetBrains, Visual Studio and Eclipse.

Paste this into Amazon Q Developer

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 Amazon Q Developer 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 the CLI (`q chat`) for the Skill path — it has the shell access the setup document needs. The IDE extension is chat-oriented and better suited to the connector route below.

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: AWS
How it connects: Plugin / Skill · MCP + OAuth
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)
Config file: ~/.aws/amazonq/cli-agents (IDE: ~/.aws/amazonq/agents/default.json)

Run this

qchat mcp add --name busabase --url https://busabase.com/api/mcp

Amazon Q Developer has a terminal-based CLI (q chat / qchat), so the Skill path applies — hand it the prompt above.

Prefer a connector?

CLI — remote servers are configured in your agent configuration file with the type and url fields:

{
  "mcpServers": {
    "busabase": {
      "type": "http",
      "url": "https://busabase.com/api/mcp"
    }
  }
}

Global CLI agent config lives at ~/.aws/amazonq/cli-agents. Manage servers with qchat mcp add | remove | list | import | status.

Using MCP with Amazon Q Developer · CLI MCP configuration · IDE MCP configuration

Known gotchas

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 Amazon Q Developer

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 Amazon Q Developer

Connect Amazon Q Developer to Busabase

AWS's generative-AI assistant for building and operating AWS applications — available as a terminal CLI and as an extension for VS Code, JetBrains, Visual Studio and Eclipse.

Paste this into Amazon Q Developer

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 Amazon Q Developer 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 the CLI (`q chat`) for the Skill path — it has the shell access the setup document needs. The IDE extension is chat-oriented and better suited to the connector route below.

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: AWS
How it connects: Plugin / Skill · MCP + OAuth
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)
Config file: ~/.aws/amazonq/cli-agents (IDE: ~/.aws/amazonq/agents/default.json)

Run this

qchat mcp add --name busabase --url https://busabase.com/api/mcp

Amazon Q Developer has a terminal-based CLI (q chat / qchat), so the Skill path applies — hand it the prompt above.

Prefer a connector?

CLI — remote servers are configured in your agent configuration file with the type and url fields:

{
  "mcpServers": {
    "busabase": {
      "type": "http",
      "url": "https://busabase.com/api/mcp"
    }
  }
}

Global CLI agent config lives at ~/.aws/amazonq/cli-agents. Manage servers with qchat mcp add | remove | list | import | status.

Using MCP with Amazon Q Developer · CLI MCP configuration · IDE MCP configuration

Known gotchas

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 Amazon Q Developer

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