Browser UI
Manage Ratel Local configuration from its loopback-only browser app.
Ratel Local includes a browser UI for common configuration tasks.
ratel-mcp ui
ratel-mcp ui --port 5731
ratel-mcp ui --no-openThe default command chooses an available port on 127.0.0.1 and opens the browser.
--no-open prints the URL instead. Stop the UI with Ctrl-C.
Launch it from the project you want to manage. Project and local scopes are unavailable when Ratel cannot discover a project root from that directory.
Walk through the UI
Add or inspect an upstream
Open Tools. Choose Add source, select user, project, or local scope, then configure stdio, HTTP, or SSE. Open an existing source to edit or remove it.
Remote sources show an authorization action when OAuth is required. The flow uses the
same local token store as ratel-mcp mcp auth.
Import or link a supported host
Open Agent Links, then choose Claude Code or Codex. Import previews native entries, scope placement, conflicts, and both write stages. Link previews the gateway entries without moving native servers.
Review conflicts before applying. Cursor is not available here; follow the manual Cursor guide.
Manage skills and the statusline
Open Skills to create a skill, move Claude Code or legacy Codex skill folders into Ratel management, edit a managed skill, or return it to its source.
The Claude Code agent page can install or remove the Ratel-owned statusline. Codex and Cursor do not use this statusline integration.
Verify and stop
Confirm the expected sources and scopes, then restart the affected host. Keep the terminal process running while you use the UI; Ctrl-C closes the local server.
What you can manage
- View, add, edit, and remove MCP servers across user, project, and local scopes.
- Start OAuth for remote upstreams.
- Import MCP entries from Claude Code or Codex, or link either host to Ratel Local.
- Create skills and move skills into or out of Ratel management.
The UI has no restore action and does not copy snapshot contents back into place. Use
ratel-mcp backup list, inspect the matching manifest, and follow the manual rollback
steps on Import or link.
Security boundary
The server binds only to 127.0.0.1. It does not listen on your LAN.
The app shell and every API request require a per-session token embedded in the launch URL. Treat that URL as a credential for the lifetime of the process. Do not forward or publish it.
Configuration writes use the same validation and backup path as CLI commands.