Zed

Register Vuesax as a context server in Zed's agent panel.

MCP & AI editors 1 min read

TL;DR · same MCP, fancier name

  • Zed calls MCP servers context servers. They go in settings.json.
  • Custom servers run as processes, so you reach the URL through mcp-remote.
  • Save the skill to .rules in the project root.

Context servers are declared in your settings.json (⌘, → Open Settings), or added from the agent panel’s settings view.

Add the server

{
  "context_servers": {
    "vuesax": {
      "source": "custom",
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.vuesax.com",
        "--header",
        "Authorization: Bearer vsx_your_key_here"
      ],
      "env": {}
    }
  }
}

Zed’s custom servers are launched as processes, so the remote HTTP endpoint is reached through the mcp-remote bridge. Node 18+ must be on your PATH.

Newer builds If your Zed version supports remote MCP servers directly, you can skip the bridge and point it at https://mcp.vuesax.com with an Authorization: Bearer vsx_… header. Check the agent settings panel — if it offers a URL field, use it.

Use it

Open the agent panel (⌘?), make sure the thread is in a mode that can call tools, then ask for what you need:

YouUse the vuesax context server: find a toast/notification component and add it to src/components/ui/, wired to a global notify() store.

Zed lists the server’s tools in the panel; a red state there means the process failed to start — hover for the error.

Install the skill

YouCall get_vuesax_skill and save it to .rules in the project root.

Zed reads .rules as project instructions. See Skills.

Troubleshooting

Zed, when Node isn't on your PATH.
  • Server won’t start — run the npx command in a terminal; you will see the real error (usually Node missing, or a proxy blocking the connection).
  • 401 — the key is missing, malformed, revoked, or not PRO.
  • Tools missing after an edit — restart Zed; context servers are launched once.