Skip to content

vscode.md

Latest commit

 

History

History
79 lines (58 loc) · 2.19 KB

vscode.md

File metadata and controls

79 lines (58 loc) · 2.19 KB
Raw

VS Code Setup

Connect Pipecat Context Hub to VS Code as an MCP server over stdio. Requires GitHub Copilot with MCP support enabled.

Prerequisites

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

Option A: Workspace config (recommended for teams)

Create .vscode/mcp.json in your project root:

{
  "servers": {
    "pipecat-context-hub": {
      "type": "stdio",
      "command": "uvx",
      "args": ["pipecat-ai-context-hub", "serve"],
      "env": {}
    }
  }
}

Note: VS Code uses "servers" (not "mcpServers") and requires an explicit "type": "stdio" field.

Option B: User settings (all workspaces)

Open your VS Code settings.json and add:

{
  "mcp": {
    "servers": {
      "pipecat-context-hub": {
        "type": "stdio",
        "command": "uvx",
        "args": ["pipecat-ai-context-hub", "serve"],
        "env": {}
      }
    }
  }
}

Verify

  1. Open your project in VS Code.
  2. Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P) and run MCP: List Servers to confirm pipecat-context-hub is listed.
  3. In Copilot Chat, set the mode to Agent and ask a question about Pipecat.

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

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

Troubleshooting

  • Server not listed: Ensure .vscode/mcp.json is in your workspace root and that "type": "stdio" is present.
  • 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.
  • MCP not available: Ensure you have VS Code 1.99+ and the GitHub Copilot extension installed. MCP support may need to be enabled in settings: "chat.mcp.enabled": true.