All agents
Busabase for Amazon Q Developer

Connect Amazon Q Developer to Busabase

Renamed: the Amazon Q Developer CLI is now the Kiro CLI. What remains is AWS's Amazon Q extension for VS Code, JetBrains, Visual Studio and Eclipse, supported until April 30, 2027, with new features shipping only in Kiro.

Busabase MCP server

https://busabase.com/api/mcp

Read the Amazon Q Developer documentation
Busabase
MCP connector
A Base of posts in a Busabase workspace, with records, views, and agent prompts

Set it up

Hosted chat has no shell and no file system, so a connector is the way in.

Add the server

Point your chat client at the Busabase MCP endpoint.

Sign in

Complete OAuth in the browser — no client id or secret to create.

Pick the smallest permission

changeRequest lets the agent propose but never merge.

Verify

Ask the agent to call auth_verify before it does any work.

Step by step

This host has no shell, so a connector is the only way in.

At a glance

Vendor
AWS
How it connects
MCP + OAuth
Transport
Streamable HTTP
Authentication
Unknown
Config file
~/.aws/amazonq/default.json (project: .amazonq/default.json)

Using the command line? The Amazon Q Developer CLI has become the Kiro CLI. Follow Connect Kiro to Busabase instead.

In the Amazon Q extension for your IDE:

  1. Open the Q Developer panel, open Chat, and choose the tools icon.
  2. Choose +, then pick a scope: global (saved to ~/.aws/amazonq/default.json) or local (.amazonq/default.json in this project).
  3. Enter busabase as the Name, select http as the transport, and enter https://busabase.com/api/mcp as the URL.
  4. Choose Save, then review the tool permissions that appear.
  5. When Busabase asks for authorization, Amazon Q opens a browser page. Sign in and approve, then ask Amazon Q to call auth_verify.

MCP configuration for Q Developer in the IDE

Known gotchas

AWS will discontinue support for the Amazon Q Developer IDE plugins on April 30, 2027, and new features ship only in Kiro. The Amazon Q CLI (`q`, `qchat`) has become the Kiro CLI, so older guides using `qchat mcp add` no longer apply. The IDE extension has no Agent Skills, so it connects over MCP only. AWS doesn't say whether the extension registers its OAuth client dynamically, which Busabase requires; not yet tested by us. AWS's older MCP overview page still describes the CLI and gives a different IDE path (`~/.aws/amazonq/agents/default.json`); this page follows the current IDE guide.

How it compares

Connection capabilities side by side with other agents already in this directory.

CapabilityAmazon Q DeveloperClaude CodeCursor
TypeIDE pluginsTerminal agentsAI editors
Recommended pathMCP connectorAgent SkillAgent Skill
How it connectsMCP + OAuthMCP + OAuth · Plugin / SkillMCP + OAuth · Plugin / Skill
TransportStreamable HTTPStreamable HTTPStreamable HTTP
AuthenticationUnknownOAuth (dynamic registration)OAuth (dynamic registration)
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 fromOfficial site

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 agent

Busabase MCP server

https://busabase.com/api/mcp