Skip to main content

​
Overview

This guide walks you through removing the ByteRover V2 MCP server configuration from Goose CLI.
We guide assume you’ve previously connected Goose CLI with ByteRover V2 via the guide here.

​
Steps

1

Toggle off Byterover MCP Server

Run goose configure in the terminal and choose Toogle Extensions option:
goose configure

This will update your existing config files
  if you prefer, you can edit them directly at /Users/byterover/.config/goose

┌   goose-configure
│
◆  What would you like to configure?
│  ○ Configure Providers
│  ○ Custom Providers
│  ○ Add Extension
│  ● Toggle Extensions (Enable or disable connected extensions)
│  ○ Remove Extension
│  ○ goose settings
└
Then, turn off byterover-mcp or the name you’ve chosen for the MCP server (hit space and then enter):
goose configure

This will update your existing config files
  if you prefer, you can edit them directly at /Users/byterover/.config/goose

┌   goose-configure
│
◇  What would you like to configure?
│  Toggle Extensions
│
◆  enable extensions: (use "space" to toggle and "enter" to submit)
│  ◼ Extension Manager
│  ◼ byterover-mcp (<)
│  ◻ chatrecall
│  ◻ code_execution
│  ◼ skills
│  ◼ todo
└
2

Remove the Byterover MCP Server

Run goose configure again and choose the Remove Extension option:
goose configure

This will update your existing config files
  if you prefer, you can edit them directly at /Users/byterover/.config/goose

┌   goose-configure
│
◆  What would you like to configure?
│  ○ Configure Providers
│  ○ Custom Providers
│  ○ Add Extension
│  ● Toggle Extensions (Enable or disable connected extensions)
│  ○ Remove Extension
│  ○ goose settings
└
Finally, choose byterover-mcp on the list or the name you’ve chosen for the MCP server (hit space and then enter):
goose configure

This will update your existing config files
  if you prefer, you can edit them directly at /Users/byterover/.config/goose

┌   goose-configure
│
◇  What would you like to configure?
│  Remove Extension
│
◆  Select extensions to remove (note: you can only remove disabled extensions - use "space" to toggle and "enter" to submit)
│  ◻ chatrecall
│  ◻ code_execution
│  ◻ byterover-mcp (<)
└
3

Remove Automated Instructions

If you have ByteRover instructions in your AGENTS.md file, remove this block:
[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
4

Verify Removal

Run goose configure again and choose the Remove Extension option:
goose configure

This will update your existing config files
  if you prefer, you can edit them directly at /Users/byterover/.config/goose

┌   goose-configure
│
◇  What would you like to configure?
│  Remove Extension
│
◆  Select extensions to remove (note: you can only remove disabled extensions - use "space" to toggle and "enter" to submit)
│  ◻ chatrecall (<)
│  ◻ code_execution
│  ◻ byterover-mcp
└
You should not see byterover-mcp in the list.

​
Need Help?

V3 Quickstart

Get started with ByteRover V3

Join Discord

Connect with our community

Email Support

Contact our support team