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

# Zed

> Set up and use the OpenCX MCP server in Zed — context_servers in settings and the Agent panel.

Zed connects to <Tooltip tip="An open standard that lets AI assistants interact with external tools and data sources.">MCP</Tooltip> servers through the `context_servers` key in your settings. Tools are used from the **Agent** panel when a compatible model is selected.

<Note>
  Zed's MCP format evolves between releases. For the authoritative schema, see [Model Context Protocol](https://zed.dev/docs/ai/mcp.html) in the Zed documentation.
</Note>

## Setup

<Steps>
  <Step title="Open Zed settings">
    Run **zed: open settings** from the command palette, or edit your user `settings.json` (for example `~/.config/zed/settings.json` on Linux, or the path shown in Zed's settings UI on macOS and Windows).
  </Step>

  <Step title="Add OpenCX under context_servers">
    Add an `opencx` entry (merge with any existing `context_servers` object):

    ```json theme={"dark"}
    {
      "context_servers": {
        "opencx": {
          "command": "npx",
          "args": ["-y", "@opencx/mcp"],
          "env": {
            "OPENCX_API_KEY": "your-api-key-here"
          }
        }
      }
    }
    ```

    Replace `your-api-key-here` with your [OpenCX API key](https://platform.open.cx/settings/access).
  </Step>

  <Step title="Confirm in the Agent panel">
    Open the Agent panel settings view and check that **opencx** shows a healthy status indicator. Then ask the agent: *"List my recent chat sessions."*
  </Step>
</Steps>

## Project-level config

You can also define MCP servers in **`.zed/settings.json`** inside a project so the team shares the same server list. Do not commit real API keys; document how each developer sets `OPENCX_API_KEY` locally.

## Tool approval

Zed may prompt before running MCP tools. Adjust tool permissions in Zed settings if you want stricter or more permissive defaults for trusted servers.

***

## Related Documentation

<CardGroup cols={2}>
  <Card title="Get Started" icon="download" href="/mcp/install">
    API key setup and all client configs
  </Card>

  <Card title="Cursor" icon="text-slash" href="/mcp/clients/cursor">
    Another editor-native MCP workflow
  </Card>

  <Card title="Prompt Library" icon="message" href="/mcp/prompts">
    Ready-to-use prompts by domain
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/mcp/troubleshooting">
    Common issues and fixes
  </Card>
</CardGroup>