Busabase for Zed

Connect Zed to Busabase

High-performance collaborative editor; MCP servers are configured as `context_servers` and it runs the standard OAuth flow.

Paste this into Zed

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 Zed documentation

Busabase

Agent Skill

Give your agent this one instruction

You end up with more than a connector: the busabase skill carries the whole approval-first 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

Zed's agent asks before running each command — approve the `npx` steps when prompted.

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: Zed Industries
How it connects: MCP + OAuth · Plugin / Skill
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)
Config file: Zed settings.json (`zed: open settings file`)

Run zed: open settings file and add Busabase under context_servers:

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

Or use Settings → AI → MCP Servers → Add Server → Add Remote Server.

With no Authorization header set, Zed prompts you to authenticate through the standard MCP OAuth flow. Then ask the agent to call auth_verify.

Known gotchas

The config key is `context_servers`, not `mcpServers`. Leave the `Authorization` header out entirely — Zed only offers to run the OAuth flow when no header is configured.

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.

Where these steps come from Official site

Let your agent do the setup

One instruction, reviewed access, and every change it makes afterwards arrives as a proposal you approve.

Browse every agent

Paste this into Zed

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

All agents

Busabase for Zed

Connect Zed to Busabase

High-performance collaborative editor; MCP servers are configured as `context_servers` and it runs the standard OAuth flow.

Paste this into Zed

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 Zed documentation

Busabase

Agent Skill

Give your agent this one instruction

You end up with more than a connector: the busabase skill carries the whole approval-first 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

Zed's agent asks before running each command — approve the `npx` steps when prompted.

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: Zed Industries
How it connects: MCP + OAuth · Plugin / Skill
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)
Config file: Zed settings.json (`zed: open settings file`)

Run zed: open settings file and add Busabase under context_servers:

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

Or use Settings → AI → MCP Servers → Add Server → Add Remote Server.

With no Authorization header set, Zed prompts you to authenticate through the standard MCP OAuth flow. Then ask the agent to call auth_verify.

Known gotchas

The config key is `context_servers`, not `mcpServers`. Leave the `Authorization` header out entirely — Zed only offers to run the OAuth flow when no header is configured.

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.

Where these steps come from Official site

Let your agent do the setup

One instruction, reviewed access, and every change it makes afterwards arrives as a proposal you approve.

Browse every agent

Paste this into Zed

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

All agents

Busabase for Zed

Connect Zed to Busabase

High-performance collaborative editor; MCP servers are configured as `context_servers` and it runs the standard OAuth flow.

Paste this into Zed

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 Zed documentation

Busabase

Agent Skill

Give your agent this one instruction

You end up with more than a connector: the busabase skill carries the whole approval-first 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

Zed's agent asks before running each command — approve the `npx` steps when prompted.

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: Zed Industries
How it connects: MCP + OAuth · Plugin / Skill
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)
Config file: Zed settings.json (`zed: open settings file`)

Run zed: open settings file and add Busabase under context_servers:

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

Or use Settings → AI → MCP Servers → Add Server → Add Remote Server.

With no Authorization header set, Zed prompts you to authenticate through the standard MCP OAuth flow. Then ask the agent to call auth_verify.

Known gotchas

The config key is `context_servers`, not `mcpServers`. Leave the `Authorization` header out entirely — Zed only offers to run the OAuth flow when no header is configured.

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.

Where these steps come from Official site

Let your agent do the setup

One instruction, reviewed access, and every change it makes afterwards arrives as a proposal you approve.

Browse every agent

Paste this into Zed

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