GoBuildWP CloudConnect your sites through one workspace.Explore Cloud →
GoBuildWP
Download freeDownload

Archived Roo Code migration guide

Roo is no longer maintained. Choose Cline or Kilo Code before setting up a new connection. Create a distinct replacement grant or expiring token, verify the required reads and any bounded staging task, then revoke Roo’s old credential. Existing-version interoperability remains untested here.

Archived VS Code extension, OAuth via mcp-remote

Roo Code WordPress MCP after the shutdown. Keep it running, then move it.

An existing Roo Code WordPress MCP connection may remain usable, but its retained build must be checked: the extension was shut down and its repository archived on 15 May 2026. This guide is for people with a WordPress server already in .roo/mcp.json who need to verify their current connection and move to a maintained client.

Get GoBuildWP free Setup steps

Checked against Roo Code's documentation on 29 September 2026, entries from GoBuildWP Free 1.18.6

By GoBuildWPContent updated How we check claims

.roo/mcp.jsonOAuth via mcp-remote
{
  "mcpServers": {
    "gobuildwp-your-site-com": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://your-site.com/wp-json/mcp/wppilot-oauth"
      ]
    }
  }
}
Status
Archived 15 May 2026
Project file
.roo/mcp.json (wins over global)
Remote type
"streamable-http"

Leaving Roo Code without losing the trail

Export what Roo did before you switch clients

A move between agents is a natural point to lose track of history: the new client knows nothing about the old one's sessions. GoBuildWP's change ledger does, because it records the agent credential and client behind every write. Before you revoke Roo's credential, ask Roo, or any working client, to run wppilot/export-changes filtered to the Roo agent. It returns flat rows of what changed, when, through which ability and whether each change can still be undone, with secrets redacted and before-images left out, so the file can sit next to the handover notes from the read-only task.

If anything in that export looks wrong, deal with it while Roo is still connected. wppilot/list-sessions shows each Roo session and how many of its changes are undoable; wppilot/undo-session reverses one session newest first and refuses, listing the conflicts, if something else edited the same targets afterwards. Undo is not tied to the client, so a session can also be undone later from the replacement.

What does not carry over to Cline or Kilo Code

The endpoint URL moves unchanged. The credential does not: the replacement gets its own token or sign-in, and Roo's is revoked last. The client-side settings around them also change, because each replacement handles approval and authentication its own way.

  • alwaysAllow: Roo's per-tool list has no equivalent in Cline, where MCP auto-approval is one switch; in Kilo Code it becomes Approve Always rules in the Permission Dock. Re-create read-only allowances deliberately.
  • OAuth: Roo needed the mcp-remote bridge. Cline and Kilo Code run the sign-in themselves, so the new entry needs no Node.js and gets its own grant in Connected Apps.
  • Transport spelling: Roo's streamable-http becomes streamableHttp in Cline and type remote in Kilo Code.
  • Timeouts: Roo's timeout was in seconds; Kilo Code's is in milliseconds with a shorter remote default, so a long audit that worked in Roo may need it raised.

Retire the credential, then the file

Revoke Roo's grant last, after the replacement has completed its required reads with a credential of its own. For a token, delete it on the GoBuildWP Connect screen; for the bridge's OAuth sign-in, revoke the entry in Connected Apps; for an Application Password, revoke it under the WordPress user's profile. Then remove the server from .roo/mcp.json, and the file from the repository if it was committed, so a teammate who still has Roo installed does not reconnect with a credential that no longer works and conclude the site is down.

FAQ

Roo Code shutdown questions

Does Roo Code still work with WordPress?

GoBuildWP still recognizes Roo Code connections by name, but no current Roo build was tested against the site for this guide, so an existing install may or may not keep connecting. The extension was shut down on 15 May 2026 and will not receive fixes, so treat it as temporary.

Where should I move a Roo Code WordPress setup?

Roo's README names Cline and the community fork ZooCode. Kilo Code also offers a Roo migration. GoBuildWP has guides for Cline and Kilo Code.

What changes in the WordPress entry when I move?

For Cline, the token entry's type becomes streamableHttp in cline_mcp_settings.json. For Kilo Code, it becomes a remote entry under mcp in kilo.jsonc. The URL stays the same; the credential should not. Give the replacement its own token or sign-in, confirm its reads work, then revoke Roo's credential.

Did Roo Code support OAuth natively?

Its documentation never described it, so GoBuildWP routes Roo's OAuth through the mcp-remote bridge.

Connect screen

What GoBuildWP still generates for Roo Code

GoBuildWP keeps Roo Code in its registry so connections stay labelled, and its Connect screen notes the discontinuation and points new setups to Cline or ZooCode. The token entry uses type streamable-http, hyphenated, which matches Roo's retained documentation. GoBuildWP generates an npx mcp-remote bridge for OAuth rather than a native flow. Neither generated shape proves compatibility with your retained Roo build or bridge version; verify discovery and an authorized read before relying on it.

OAuth 2.1 through mcp-remoteThe only OAuth route for Roo: the npx bridge runs the sign-in. Needs Node.js.
Access tokentype streamable-http with url and headers. Simplest to carry to another client later.
Application PasswordThe npx bridge with credentials in env.

Endpoints on your site: /wp-json/mcp/wppilot-oauth for OAuth, /wp-json/mcp/wppilot for tokens and passwords. Through the optional GoBuildWP Cloud instead, every client uses https://app.gobuildwp.com/mcp with the server name gobuildwp, and a personal Cloud token is read from GOBUILDWP_TOKEN where the client supports environment variables.

.roo/mcp.jsonAccess token
{
  "mcpServers": {
    "gobuildwp-your-site-com": {
      "type": "streamable-http",
      "url": "https://your-site.com/wp-json/mcp/wppilot",
      "headers": {
        "Authorization": "Bearer wpp_YOUR-ACCESS-TOKEN"
      }
    }
  }
}

Setup

Keep an existing Roo Code connection working

No new Roo Code releases will fix anything, so keep the setup plain and plan the move.

  1. Check which file wins

    Roo reads a global mcp_settings.json and the project's .roo/mcp.json; the project file takes precedence. Use Edit Global MCP or Edit Project MCP in the MCP panel to open each.

  2. Use distinct migration credentials

    A token route can avoid the local Node.js bridge. Mint a separate expiring token or grant for the replacement client; do not copy Roo's existing credential into it.

  3. Set approvals per tool

    Roo's alwaysAllow list on the entry pre-approves named tools and disabledTools hides them. Put only WordPress reads in alwaysAllow.

  4. Plan the move

    Roo's README points to Cline and to ZooCode, a community fork. Kilo Code runs its own Roo migration tool that merges Roo settings into its configuration.

  5. Verify before revoking

    Verify required reads and any separately authorized bounded staging task in the replacement client, then revoke Roo's distinct old token or grant. This changes access, not WordPress content; review and redact any optional local handover file before sharing it.

Verify the connection before allowing changes

Select Read Only explicitly; the default is Production Safe. Use a dedicated identity with manage_options on a single site, or superadmin on multisite. Match the named tool call, site URL and returned record ID against WordPress.

First connection checkRead Only
Use the gobuildwp-your-site-com MCP server in Roo Code. Do not change anything.

1. Report the active GoBuildWP safety profile.
2. List the abilities this connection can see.
3. Call wppilot/get-site-settings and report the site URL and locale.
4. Call wppilot/list-content for the five newest pages,
   then wppilot/get-content on one of them.
5. Name every ability you called and each WordPress ID you read.

These setup instructions are not a recorded live-client test. Keep credentials out of repositories, logs and shared files.

Troubleshooting

Roo Code errors and their causes

SymptomCause and fix
The project server is ignoredA global server with the same name is not the cause; the project file wins. Check the JSON is valid and the MCP panel shows it enabled.
streamableHttp is rejectedRoo spells it streamable-http with a hyphen. Cline is the client that uses camel case.
The bridge fails to startNode.js is missing or npx cannot fetch mcp-remote. Switch to the token entry.
Long audits time outRaise timeout on the entry, in seconds. The default is 60.

Inside Roo Code

Checking a Roo connection that nobody maintains

The MCP panel lists servers with an enable switch and their tools. timeout on the entry is in seconds, from 1 to 3,600, default 60; a WordPress audit that runs longer needs it raised. watchPaths restarts a local server when named files change, which matters only for the npx bridge.

Because the extension will not be updated, VS Code or protocol changes may eventually break it without warning. GoBuildWP serves the older 2025-11-25 protocol revision to clients that predate 2026-07-28, but an existing Roo build was not tested here. Verify required reads on the replacement client with distinct new credentials before revoking the old grant.

Keep an eye on GoBuildWP's connection list: the Overview screen labels Roo Code connections by name, so you can tell when the last one has gone.

Signs it worked

  • The server is enabled in Roo's MCP panel
  • alwaysAllow contains reads only
  • A replacement client is connected
  • The Roo credential is revoked after the move

First task

A last task: export what the new client needs

Before moving, have Roo record the site facts you would otherwise rediscover. It reads only.

Roo Code promptReads only
Use the WordPress MCP server. Read only.

Collect, for handover to another agent:
- wppilot/agent-context (profile, role)
- wppilot/get-site-settings (URL, locale)
- wppilot/list-extensions (active theme, plugins)
- wppilot/skill-get for any site skill in use
Write it as a short markdown file in this repo.

Related

Where to go next

  • Cline: named by Roo as a migration target, with native OAuth
  • Kilo Code: migrates Roo settings into kilo.jsonc
Every client guide (26)

Roo Code documentation read on 29 September 2026

Keep Roo Code connected until the move is done.

Use a token with an expiry, pick Cline or Kilo Code, then revoke the old credential.

Get GoBuildWP free See Pro pricing