> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ascendgtm.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect to Zed

> Add V5 Gateway as an MCP server in the Zed editor

## Prerequisites

* Zed installed (zed.dev) — version 0.130.0 or later (MCP support added)
* A V5 bearer token — get one from `POST /admin/tokens/issue`

## Setup

<Steps>
  <Step title="Open Zed settings">
    Press `⌘,` to open Settings, or edit `~/.config/zed/settings.json` directly.
  </Step>

  <Step title="Add MCP server">
    ```json ~/.config/zed/settings.json theme={null}
    {
      "context_servers": {
        "ascend": {
          "settings": {
            "url": "https://ascend-gateway-v5.ascendgtm.workers.dev/mcp",
            "headers": {
              "Authorization": "Bearer <your-token>"
            }
          }
        }
      }
    }
    ```
  </Step>

  <Step title="Verify in Zed AI panel">
    Open the AI panel (`⌃⌘Enter`) and ask: *"List my HubSpot deals in Stage: Proposal."*

    Zed should call `hubspot_crm` and return the deals.
  </Step>
</Steps>

## Notes

* Zed uses the term "context servers" for MCP servers — same protocol, different label
* Token is stored in plaintext in `settings.json` — use a read-only scoped token if sharing workspaces
* For team setups, create a project-level `.zed/settings.json` with a shared read-only token