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