Busabase for Amp

Connect Amp to Busabase

Sourcegraph's agentic coding tool — a terminal TUI with full shell, file editing and git access, plus editor extensions.

Paste this into Amp

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 Amp Skills documentation
Busabase
Agent Skill
A Base of posts in a Busabase workspace, with records, views, and agent prompts

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.

Install the Busabase skills
npx skills add busabase/skills

For this agent

Amp's TUI runs shell commands directly, so the setup document works without extra configuration.

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.

Amp MCP documentation

At a glance

Vendor
Sourcegraph
How it connects
Plugin / Skill · MCP + OAuth
Transport
Streamable HTTP
Authentication
OAuth (dynamic registration)
Config file
~/.config/amp/settings.json (or settings.jsonc; Windows: %USERPROFILE%\.config\amp\settings.json)
Run this
amp mcp add busabase https://busabase.com/api/mcp

Amp is a terminal-based coding agent with full filesystem and shell access, so the Skill path applies.

Prefer a connector?

Add the server from the CLI:

amp mcp add busabase https://busabase.com/api/mcp

Or edit ~/.config/amp/settings.json (.jsonc also works) directly — note the key is amp.mcpServers, not a bare mcpServers:

{
  "amp.mcpServers": {
    "busabase": {
      "url": "https://busabase.com/api/mcp"
    }
  }
}

Amp's manual states that for servers supporting automatic OAuth client registration, "when you start the Amp TUI after adding such a server, Amp will automatically start the OAuth flow in your browser." Busabase supports dynamic client registration, so this should apply.

Other commands: amp mcp doctor (check status), amp mcp approve <name> (approve workspace servers), amp mcp oauth login|logout <name> (manual credential handling).

Amp manual

Known gotchas

The settings key is `amp.mcpServers` — a bare `mcpServers` (the shape most other clients use) is not read. OAuth starts automatically when you launch the TUI after adding a server that supports dynamic registration; `amp mcp oauth login <name>` handles it manually if that does not fire, and `amp mcp doctor` diagnoses a failing connection. The MCP docs have moved from ampcode.com/manual to ampcode.com/docs/customize/mcp: Amp now tries a Client ID Metadata Document (CIMD) first and falls back to dynamic client registration, so auth-mode stays oauth-dynamic-registration for Busabase. Browser-based OAuth is unavailable in orbs (Amp's headless environments) — use headers/secrets or remote MCP definitions there. The settings file can also be settings.jsonc (Windows: %USERPROFILE%\.config\amp\settings.json).

How it compares

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

CapabilityAmpClaude CodeCursor
TypeTerminal agentsTerminal agentsAI editors
Recommended pathAgent SkillAgent SkillAgent Skill
How it connectsPlugin / Skill · MCP + OAuthMCP + OAuth · Plugin / SkillMCP + OAuth · Plugin / Skill
TransportStreamable HTTPStreamable HTTPStreamable HTTP
AuthenticationOAuth (dynamic registration)OAuth (dynamic registration)OAuth (dynamic registration)
These stepsFrom official docsLast checked Nov 10, 2026

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 agent

Paste this into Amp

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