MCP servers

Ropenode can attach MCP servers to a Claude Code session, so the agent gets browser control or design-file access without you wiring it up per project. MCP servers are a Pro feature, set per project in Project settings → MCP.

What this actually is

Be clear on the scope, because "MCP support" is a phrase that promises more than this:

Ropenode manages a fixed set of two servers — Playwright and Figma. It is not a general "add any MCP server" manager.

Enable them and Ropenode generates the MCP config the CLI is launched with. Tokens you provide are sealed with AES-256-GCM like every other secret.

Playwright drives your real Chrome

The Playwright server drives the Chrome you already use. Two sessions driving the same browser collide without any error — every step "succeeds", on the wrong page — so there is a switch to let only one session drive the browser at a time.

Conflicts with your own config

If you already run the same server globally, two copies would be launched and the agent would see duplicate tools with the same names — which it handles badly and unpredictably. Ropenode detects an existing entry in your ~/.claude.json and offers to remove it, rather than quietly winning or quietly losing.

Adding your own servers

Not through Ropenode today. Configure them in your CLI's own config as usual; Ropenode does not remove or override entries it did not add.

Codex

A Codex session does not get Ropenode's MCP servers: Codex reads MCP servers from its own configuration.

WSL

A WSL project runs its CLI inside the distro as the project-owning user, which is why user-scope MCP servers installed there are visible. The Playwright server itself runs on Windows, where your browser is, so it needs Node.js (npx) on Windows. See How WSL projects work.