Zed

Using Kernel CLI (recommended):

kernel mcp install --target zed

Compare the installed Kernel entry with the manual example below. Add any missing OAuth metadata, callback port, or cache directory before authorizing. Manual setup:

Press ⌘/Ctrl , to open settings.
Paste this Linux example, changing the cache path to an absolute directory in your home directory:

{
  "context_servers": {
    "kernel": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.onkernel.com/mcp", "46097", "--static-oauth-client-metadata", "{\"client_name\":\"Zed\"}"],
      "env": {"MCP_REMOTE_CONFIG_DIR": "/home/user/.mcp-auth/kernel-zed"}
    }
  }
}

Each client needs a separate MCP_REMOTE_CONFIG_DIR and OAuth callback port. The 46097 argument sets Zed’s port so it can authorize while other clients are running. The CLI preserves an existing explicit port; if you customize it, choose an unused port that no other client uses. If you previously authorized Kernel and the consent screen still shows MCP CLI Proxy, close Zed, update the config above, then remove the cache it used (~/.mcp-auth/mcp-remote-v1/ by default, or mcp-remote-v1/ under your custom MCP_REMOTE_CONFIG_DIR). Reopen Zed and authorize again. This also signs out other clients using that cache.

Getting Started

Connect Your Client

Tools

Resources & Prompts

Reference