Busabase for GitHub Copilot CLI

Connect GitHub Copilot CLI to Busabase

GitHub's terminal coding agent (the `copilot` command) that reads, edits, and runs code in your local repo with your GitHub account and Copilot subscription.

Paste this into GitHub Copilot CLI

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 GitHub Copilot CLI 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.

For this agent

Copilot CLI asks you to approve shell commands before it runs them, so approve the `npx busabase-cli login --no-wait` and `npx skills add ...` steps. It discovers personal skills in `~/.copilot/skills/` and `~/.agents/skills/` and project skills in `.github/skills/`, `.agents/skills/`, or `.claude/skills/`; run `/skills reload` (or start a new session) after installing, and `/skills list` to confirm `busabase` is loaded. Skills can also be added with `copilot skill add <file|URL|dir>`.

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
GitHub
How it connects
Plugin / Skill · busabase-cli · REST API · MCP + OAuth · MCP + API key
Transport
Streamable HTTP
Authentication
OAuth (dynamic registration)
Config file
~/.copilot/mcp-config.json
Run this
npm install -g @github/copilot
brew install --cask copilot-cli
winget install GitHub.Copilot
curl -fsSL https://gh.io/copilot-install | bash

GitHub Copilot CLI runs shell commands in your terminal, so the Skill path applies: paste the prompt above into a copilot session and approve the commands it asks to run.

Prefer a connector?

Copilot CLI can add a remote MCP server that signs in with OAuth.

  1. Add the server from your terminal:

    copilot mcp add --transport http busabase https://busabase.com/api/mcp
    

    Or, inside a session, run /mcp add, enter busabase as Server Name, choose HTTP, paste https://busabase.com/api/mcp as URL, keep Tools as *, and press Ctrl+S.

    Or edit ~/.copilot/mcp-config.json yourself:

    {
      "mcpServers": {
        "busabase": {
          "type": "http",
          "url": "https://busabase.com/api/mcp",
          "tools": ["*"]
        }
      }
    }
    
  2. Start copilot. When the server needs sign-in it shows needs-auth; run /mcp auth busabase to open the browser, approve Busabase, and the server reconnects.

  3. Ask it to call auth_verify.

To use a Busabase API key instead of OAuth, add --header "Authorization: Bearer YOUR-BUSABASE-API-KEY" to the copilot mcp add command (or a headers object in the JSON).

GitHub Docs: Adding MCP servers for GitHub Copilot CLI

Known gotchas

- Requires an active GitHub Copilot subscription; an org or enterprise admin can disable Copilot CLI, and an org MCP allowlist policy can block servers that are not on it. - OAuth sign-in for a remote server is triggered with `/mcp auth <server-name>` when it shows `needs-auth`; it opens a browser. On headless/SSH machines GitHub documents a device-code fallback. - Copilot CLI does not read `.vscode/mcp.json` (VS Code's `servers` key is unsupported). Project-level `.mcp.json` / `.github/mcp.json` load only after you trust the folder. - Since 1.0.66, setting `COPILOT_HOME` or `--config-dir` stops skills loading from `~/.agents/skills`; use `~/.copilot/skills` (or the custom home's `skills/`) in that case.

How it compares

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

CapabilityGitHub Copilot CLIClaude CodeCursor
TypeTerminal agentsTerminal agentsAI editors
Recommended pathAgent SkillAgent SkillAgent Skill
How it connectsPlugin / Skill · busabase-cli · REST API · MCP + OAuth · MCP + API keyMCP + OAuth · Plugin / SkillMCP + OAuth · Plugin / Skill
TransportStreamable HTTPStreamable HTTPStreamable HTTP
AuthenticationOAuth (dynamic registration)OAuth (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.

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 GitHub Copilot CLI

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