> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/balkanid-mcp/installation-and-setup/zed.md).

# Zed

Connect [Zed](https://zed.dev/docs/ai/mcp) to BalkanID MCP.

**OAuth is preferred.** API keys remain available for Read-only or static-token setups.

### One-click (OAuth — recommended)

1. Open <https://mcp.balkanid.app>, sign in, and confirm the correct **tenant**.
2. Under **OAuth Connectors**, select **Zed**.
3. Click **Copy settings JSON**. The snippet adds a `context_servers.balkanid` entry with the BalkanID MCP URL (no `Authorization` header — Zed runs MCP OAuth when needed).
4. In Zed, open **Settings → AI → MCP Servers**, or run **Command Palette** → `zed: open settings file`.
5. Merge the copied `context_servers` block into your settings and save. Zed reloads MCP configuration.
6. If `balkanid` shows an **Authenticate** control, click it and complete BalkanID sign-in and tenant consent in your browser.

{% hint style="info" %}
OAuth currently requires **both Read and Write** scopes. See Authentication and Permissions.
{% endhint %}

### Manual configuration (OAuth fallback)

Edit [Zed MCP settings](https://zed.dev/docs/ai/mcp) directly (`settings.json`) with:

```json
{
  "context_servers": {
    "balkanid": {
      "source": "custom",
      "url": "https://mcp.balkanid.app/server/mcp"
    }
  }
}
```

Save, then use **Authenticate** in **Settings → AI → MCP Servers** if Zed prompts you.

### One-click (API key)

1. Create an API key in the [MCP UI](https://mcp.balkanid.app) under **Bearer Auth Keys**.
2. Open **Connect** for that key, choose **Zed**, and copy the `context_servers` JSON (includes the Bearer header).
3. Merge into `settings.json` under `context_servers` and save.

### Manual configuration (API key fallback)

```json
{
  "context_servers": {
    "balkanid": {
      "source": "custom",
      "url": "https://mcp.balkanid.app/server/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}
```

Replace `YOUR_TOKEN_HERE` with the token from the MCP UI. Use a Read-only key when you only need discovery tools.

### Verify

Ask Zed's Agent: “Call whoami on BalkanID MCP.” You should see your email and tenant ID.

### Disable or remove

Open **Settings → AI → MCP Servers**, find `balkanid`, and remove it from the list — or delete the `context_servers.balkanid` block from `settings.json` directly and save.

### Official documentation

Zed documentation for MCP servers:

* [Model Context Protocol](https://zed.dev/docs/ai/mcp) — Zed Docs


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.balkan.id/balkanid-mcp/installation-and-setup/zed.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.