Connect Agentastic.dev to Busabase
Agentastic.dev is a native macOS multi-agent IDE that runs coding-agent CLIs such as Claude Code, Codex, Gemini and Cursor side by side, each in its own git worktree, container or cloud VM.
Paste this into Agentastic.dev
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

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.
npx skills add busabase/skillsFor this agent
Agentastic also has its own skill library (Settings → Skills), which copies attached skills into the worktree for Prime Agent, Claude Code, Codex, Poolside, Droid and Amp. Its Install from GitHub "finds the first SKILL.md in the repo", so it may not pick the `busabase` skill from `busabase/skills`. The prompt above is the reliable route.
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
- Agentastic.ai
- How it connects
- Plugin / Skill · busabase-cli · REST API · MCP + API key
- Transport
- Streamable HTTP
- Authentication
- API key
- Config file
- Settings → Plugins → Add MCP Server (personal plugins stored under ~/Library/Application Support/Agentastic.dev/Plugins/; workspace plugins at .agentastic/plugins/)
Agentastic runs each provider's real CLI (Claude Code, Codex, Gemini, Cursor and 50+ more) in a terminal, so the Skill path applies: start an agent in Agent Home and paste the prompt above ("Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me"). The skill lands wherever that CLI keeps skills. For per-agent details see Claude Code, Codex or OpenCode.
Prefer a connector?
Agentastic can hand one MCP server to every compatible agent it launches. The documented direct route is a URL + header server with a Busabase API key (Agentastic itself does not run OAuth — for a server whose sign-in belongs to the agent it documents an agent-delegated auth.kind: "agent-oauth" mode, which does not implement OAuth itself):
Create a key in Busabase Settings → API Keys with the smallest permission that works and a finite expiration.
- Open Settings → Plugins → Add MCP Server.
- Name:
busabase. URL:https://busabase.com/api/mcp. - Add a header
Authorizationwith the valueBearer <your Busabase API key>, and mark it as a credential so it's stored in the macOS Keychain. - Save, then launch a new agent and ask it to call
auth_verify. Plugin MCP now reaches Agentastic's own agent, Claude Code, Codex, OpenCode, Amp, GitHub Copilot, Charm (Crush), Droid, Prime Agent, Qwen Code, CodeBuddy and MiMo — Agentastic writes each one's native format at launch.
Cursor and Grok don't receive plugin MCP yet (they read MCP servers only from files in your home directory). For other agents, add Busabase in their own config, or use the Skill path.
Agentastic docs: Plugins & MCP
Known gotchas
macOS only. Plugin MCP servers now reach twelve agent types — Agentastic's own agent, Claude Code, Codex, OpenCode, Amp, GitHub Copilot, Charm (Crush), Droid, Prime Agent, Qwen Code, CodeBuddy and MiMo; only Cursor and Grok are explicitly excluded (they read MCP servers only from files in your home directory). New plugins apply to agents launched after you connect them, not to sessions already running. Agentastic itself does not run OAuth: sign-in can be delegated to the agent via `auth.kind: "agent-oauth"` (Agentastic neither issues nor refreshes those tokens), so the documented direct route remains an API-key header.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | |||
|---|---|---|---|
| Type | Desktop apps | Terminal agents | AI editors |
| Recommended path | Agent Skill | Agent Skill | Agent Skill |
| How it connects | Plugin / Skill · busabase-cli · REST API · MCP + API key | MCP + OAuth · Plugin / Skill | MCP + OAuth · Plugin / Skill |
| Transport | Streamable HTTP | Streamable HTTP | Streamable HTTP |
| Authentication | API key | OAuth (dynamic registration) | OAuth (dynamic registration) |
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 agentPaste this into Agentastic.dev
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.