Skip to main content

Overview

This guide walks you through removing the ByteRover V2 MCP server configuration from GitHub Copilot in VS Code.
We guide assume you’ve previously connected GitHub Copilot with ByteRover V2 via the guide here.
If you have the ByteRover VSCode extension installed, use this automated approach:
1

Clean Up & Migrate

Open the ByteRover extension and click “Clean Up & Migrate”:Clean Up & MigrateThis will automatically remove the MCP configuration and rule file.
2

Uninstall ByteRover Extension

Uninstall the ByteRover extension:Uninstall Extension
3

Verify Removal

Restart VS Code Copilot and verify that byterover-mcp is no longer listed in tool list.

Option 2: Manual Cleanup

1

Remove ByteRover MCP Server

First, open Github Coplot and click on the icon below:VS Code SettingsThen, under the tool list, look for byterover-mcp and click on the setting icon:MCP SettingsRemove the byterover-mcp entry from the MCP servers list:Remove ByteRover MCP
2

Remove Automated Instructions

If you have ByteRover instructions in your .github/copilot-instructions.md file, delete the following content:
[byterover-mcp]

You are given two tools from Byterover MCP server, including
## 1. `byterover-store-knowledge`
You `MUST` always use this tool when:

+ Learning new patterns, APIs, or architectural decisions from the codebase
+ Encountering error solutions or debugging techniques
+ Finding reusable code patterns or utility functions
+ Completing any significant task or plan implementation

## 2. `byterover-retrieve-knowledge`
You `MUST` always use this tool when:

+ Starting any new task or implementation to gather relevant context
+ Before making architectural decisions to understand existing patterns
+ When debugging issues to check for previous solutions
+ Working with unfamiliar parts of the codebase
3

Verify Removal

Restart VS Code Copilot and verify that byterover-mcp is no longer listed in tool list.

Need Help?