npm exec -y --package busabase-cli@latest -- busabase-cli login --device-code

Pi has bash access and discovers Agent Skills from ~/.agents/skills and project .agents/skills, so the Skill path applies: ask Pi Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me.

Prefer a connector?

Pi now documents remote MCP servers. Add Busabase to ~/.pi/agent/mcp.json (user-level; a project .pi/mcp.json entry with the same name overrides it, but only after you grant that project trust):

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

or from the shell:

pi mcp add busabase --url https://busabase.com/api/mcp

Run pi mcp login busabase (or /mcp → select busabase → Sign in, in a session) to complete OAuth. Pi registers its own OAuth client automatically — no client id or secret needed — and requests whatever scope Busabase's server advertises, so you do not need to set oauth.scope. Sign out with pi mcp logout busabase.

Ask the agent to call auth_verify to confirm the connection.

For a manual fallback or scripted use, busabase-cli and the REST API at /api/v1 still work:

npm exec -y --package busabase-cli@latest -- busabase-cli login --device-code
npx busabase-cli bases list

Pi — MCP servers