Skip to content

zed.md

Latest commit

 

History

History
59 lines (41 loc) · 1.83 KB

zed.md

File metadata and controls

59 lines (41 loc) · 1.83 KB
Raw

Zed Setup

Connect Pipecat Context Hub to Zed as an MCP server over stdio. MCP tools are available in Zed's Agent panel.

Prerequisites

  • Python 3.11+
  • Zed with Agent panel support
  • uv package manager

Build the Local Index

Build the local index before serving. The first run downloads the package, models, and sources — allow a few minutes:

uvx pipecat-ai-context-hub refresh

This populates ~/.pipecat-context-hub/.

Configure

Zed uses a global settings file — there is no project-level MCP config.

Edit ~/.config/zed/settings.json (open with zed: open settings from the command palette):

{
  "context_servers": {
    "pipecat-context-hub": {
      "source": "custom",
      "command": "uvx",
      "args": ["pipecat-ai-context-hub", "serve"],
      "env": {}
    }
  }
}

Note: Zed uses "context_servers" (not "mcpServers") and requires "source": "custom" for manually configured servers.

Verify

  1. Open Zed and open the Agent panel.
  2. The server should appear in the MCP server list. Check for any error indicators.
  3. Ask the agent a question about Pipecat — the server's tools should be invoked.

You can also verify the server starts correctly from the command line:

uvx pipecat-ai-context-hub serve --help

Troubleshooting

  • Server not appearing: Ensure the context_servers key is at the top level of settings.json and that "source": "custom" is included.
  • Command not found: Ensure uv is installed and on your PATH (uvx ships with uv).
  • Empty results: Run uvx pipecat-ai-context-hub refresh to populate the index.
  • JSON parse errors: Zed's settings.json contains other settings — make sure you merge the context_servers block rather than replacing the entire file.