Zed

Zed connects to Zephex with a native remote MCP server entry in `settings.json`. The config contains only the URL, and Zed opens the OAuth browser flow automatically when no Authorization header is present.

OVERVIEW

Zed is a high-performance, GPU-accelerated code editor built in Rust. It supports remote MCP servers natively, with no bridge packages required. When a remote MCP server URL has no Authorization header in the config, Zed automatically detects the missing auth and prompts the OAuth browser flow using the standard MCP OAuth 2.0 spec. No API key is needed in the config file.

CONFIG FILE LOCATION

~/.config/zed/settings.json. This is Zed's global settings file. MCP servers go under the `context_servers` key.

PREREQUISITES

Zed installed from https://zed.dev.
A Zephex account at zephex.dev/signup.
No API key needed. Authentication is handled through the OAuth browser flow.

CONFIG

Add the `context_servers` block shown below inside your existing `settings.json`. Merge it with your current settings instead of replacing the whole file.

Do not add an `Authorization` key inside `context_servers.zephex`. Zed only triggers the OAuth browser flow when the remote server entry has no auth header.

~/.config/zed/settings.json

{  "context_servers": {    "zephex": {      "url": "https://zephex.dev/mcp"    }  }}

AUTH

Open ~/.config/zed/settings.json.
Add the `context_servers` block shown above and merge it with your existing settings.
Save the file.
Zed reloads MCP servers automatically, so no restart is needed.
On first connection, Zed detects no Authorization header and opens a browser OAuth prompt.
Log in to your Zephex account in the browser.
After login, Zed stores the token and the connection shows as active in the Agent Panel.

VERIFY

Confirm the server from Zed's Agent Panel before you rely on it in prompts.

Open the Agent Panel with `Cmd+Shift+A` on macOS.
Open the top-right menu and confirm "zephex" is listed as a connected server.
Ask the Zed AI agent what tools are available. You should see all 10 Zephex tools.

COMMON ISSUES

OAuth prompt did not appear

Make sure there is no `Authorization` key inside `context_servers.zephex`. Zed only triggers OAuth when no header is present. If you previously added a Bearer header, remove it.

Connection times out without opening a browser

Update Zed to the latest version. The OAuth trigger had a known bug in older builds that could time out silently.

Settings merge conflict

If your `settings.json` already has a `context_servers` key, add the `zephex` entry inside it instead of creating a second `context_servers` block.

"Waiting for Context Server" indefinitely

Toggle the server off and on in Zed's Agent Panel settings, or run the `zed: reload` command from the command palette.

If the editor still does not connect, return to Quickstart or check Connection Issues.