Skip to content

Latest commit

 

History

History
86 lines (63 loc) · 2.21 KB

File metadata and controls

86 lines (63 loc) · 2.21 KB

Connecting Pieces MCP to GitHub Copilot

Tool type: AI coding assistant (VS Code extension) Website: github.com/features/copilot Transport support: stdio, SSE, Streamable HTTP (via VS Code's MCP support)


Setup

GitHub Copilot uses VS Code's built-in MCP server configuration. Create or edit .vscode/mcp.json in your project:

Local Setup (recommended when PiecesOS is on the same machine)

{
  "servers": {
    "pieces": {
      "type": "http",
      "url": "http://localhost:39300/model_context_protocol/2025-03-26/mcp"
    }
  }
}

Or using SSE:

{
  "servers": {
    "pieces": {
      "type": "sse",
      "url": "http://localhost:39300/model_context_protocol/2024-11-05/sse"
    }
  }
}

Remote Setup (ngrok)

Use this when VS Code / Copilot is running on a different machine from PiecesOS. For setup, see: Connecting to PiecesOS from the Outside World via Ngrok.

{
  "servers": {
    "pieces": {
      "type": "http",
      "url": "https://YOUR_NGROK_URL.ngrok.app/model_context_protocol/2025-03-26/mcp"
    }
  }
}

Verification

  1. Open VS Code with the GitHub Copilot Chat extension active
  2. Run "MCP: List Servers" from the Command Palette
  3. Confirm "pieces" is connected
  4. In Copilot Chat, ask about your work history

Troubleshooting

Issue Solution
MCP tools not available Ensure GitHub Copilot Chat extension is up to date
Server not connecting Check PiecesOS port; try both http and sse types
Agent mode needed MCP tools may only be available in Copilot's agent mode, not inline suggestions

Related Guides


  ← Back to All Agent Setup Guides