# Remove the agent setup

Source: https://docs.fortrabbit.com/platform/automation/uninstall
Published: 2026-10-28
Updated: 2026-10-28

> Remove the fortrabbit MCP server, agent skill and frbit CLI from a coding agent, and revoke its connection in the dashboard.


## CLI

Set up with `agents.sh` or the frbit CLI? One command removes the MCP server and the skill from Claude Code and Codex, the Claude Code plugin, the CLI sign-in, its folders and the binary, through `brew` or `npm` when installed that way:



```shell
frbit uninstall
```

It lists what it removes and asks first, `--yes` skips the question. On Windows, finish with the step it prints. `frbit setup agent --remove` undoes the agent setup only and keeps the CLI.

Both commands need CLI 1.10.0 or later. With an older version, undo the agent setup and sign out while the binary is still in place:



```shell
frbit mcp remove --yes
frbit skills remove --yes
frbit auth logout
```

Then remove the binary with the counterpart of the install method:



```shell
# install script or release archive
rm "$(command -v frbit)"

# Homebrew
brew uninstall frbit

# npm
npm uninstall --global @fortrabbit/cli
```

Then delete the config and cache folders, which hold the saved API host, a lock file and the last update check, no tokens:

| System  | Config folder                         | Cache folder             |
| ------- | ------------------------------------- | ------------------------ |
| macOS   | `~/Library/Application Support/frbit` | `~/Library/Caches/frbit` |
| Linux   | `~/.config/frbit`                     | `~/.cache/frbit`         |
| Windows | `%AppData%\frbit`                     | `%LocalAppData%\frbit`   |

## Prompt

An agent set itself up from the prompt? Paste this prompt and it removes what it installed:



```txt
Read https://www.fortrabbit.com/agents.md and remove the fortrabbit setup.
```

## MCP server

claude.ai and Claude Desktop: Settings → Connectors, open fortrabbit and remove it.

In the other clients, log out first, then remove the server. Logging out after the removal no longer works, because the client has forgotten the server. The login holds the stored credentials, which live outside the config file:



```shell
claude mcp logout fortrabbit
claude mcp remove fortrabbit

codex mcp logout fortrabbit
codex mcp remove fortrabbit
```

| Client      | Remove with                                         |
| ----------- | --------------------------------------------------- |
| Claude Code | `claude mcp remove fortrabbit`                      |
| Codex       | `codex mcp remove fortrabbit`                       |
| Cursor      | Delete the entry from `~/.cursor/mcp.json`          |
| VS Code     | `MCP: List Servers`, or edit the profile `mcp.json` |
| frbit CLI   | `frbit mcp remove --yes`                            |

`claude mcp remove` needs no scope, it takes the server out of whichever scope holds it. VS Code has no counterpart to `code --add-mcp`, so removal happens in the editor or in the file.

## Agent skills

Remove the skill the way it was installed:



```shell
# frbit CLI, with --project or --agent as at install
frbit skills remove --yes

# GitHub CLI, which has no remove: delete the skill folder
rm -r ~/.claude/skills/fortrabbit

# npx
npx skills remove fortrabbit
```

`--yes` skips the confirmation, which an agent can't answer. Removing the skill leaves the MCP server in place, see above.

## Claude Code plugin

`frbit uninstall` removes the plugin too. Without the CLI:



```shell
claude plugin uninstall fortrabbit@fortrabbit
claude plugin marketplace remove fortrabbit
```

## Dashboard

Removing the setup from a machine leaves the grant on the account. Revoke it under AI agents, in the account menu of the dashboard:

[Disconnect an AI agent](/disconnect/ai-agent)

This also works when the machine running the agent is out of reach.

---

- [Agent setup](/platform/automation/agents)
- [MCP server](/platform/automation/mcp)
- [CLI](/platform/automation/cli)
- [Agent skills](/platform/automation/agent-skills)