Introduction
Ratel Local — MCP Gateway that fronts Claude Code / Codex / Cursor with capability search.
Ratel Local is one MCP server for your whole tool estate. It connects to your upstream MCP servers and exposes a small, searchable capability surface to Claude Code, Codex, Cursor, or any other MCP client.
Your client sees search_capabilities and invoke_tool, plus get_skill_content when
skills are configured and auth for authorizing OAuth upstreams.
Upstream tool schemas stay out of context until a search makes them relevant.
Ratel Local is the gateway host in Ratel's architecture. The capability contracts belong to progressive disclosure; Ratel Local owns host setup, upstream configuration, authentication, and operation.
Quickstart
Start fresh with the plugin, or migrate an existing Claude Code or Codex setup.
Cursor
Add Ratel Local to Cursor manually through its standard mcp.json configuration.
MCP servers
Configure scopes, add upstreams, and verify the running gateway.
Import or link
Move native MCP entries into Ratel Local or connect a host without migrating them.
Browser UI
Manage local configuration in a loopback-only browser app.
Managing skills
Move agent skills behind retrieval and wire the prompt-time preload hook.
OAuth upstreams
Authorize remote servers, inspect status, and recover from a 401.
Statusline & telemetry
Inspect local events and show estimated context savings in Claude Code.
Embed as a library
Build and serve a Ratel Local gateway from your own Node process.
Troubleshooting
Recover from host, upstream, authentication, scope, and telemetry failures.
Ratel Local or an SDK?
Use Ratel Local when your tools already live behind MCP servers and you do not own the agent loop. Use a Ratel SDK when you want in-process catalog control, local function tools, or framework wiring. Both expose the same capability-tool contract.
Ratel Local ships as
@ratel-ai/mcp-server. The CLI binary is
ratel-mcp and requires Node.js 20 or newer.