← Back to directory
R

Reloaderoo

Community
Powerful MCP debugging proxy and CLI inspection tool
GitHub source repository ↗
★ 126 Stars Category · Dev Tools Popular Source revision 53edc55964df
66FMRS · C
Reliability
9/20
Security and permissions
12/20
Maintenance
14/20
Documentation
16/20
Setup experience
15/20

Reloaderoo provides convenient debugging and hot-reload functionality for MCP developers. CLI mode is especially suited for AI agents, and proxy mode integrates seamlessly into development workflows.

Read the FMRS scoring method →

Reloaderoo is a dual-mode MCP development tool that acts as both a CLI inspection tool and a transparent proxy server. It enables hot-reloading of MCP servers without disconnecting AI clients, and provides extensive CLI commands for direct inspection and testing of MCP servers.

Tools

restart_server
Restart the MCP server process to load code changes
list_tools
List all available tools on the server
call_tool
Call a specific tool and return the result
list_resources
List all available resources
read_resource
Read the content of a specific resource
list_prompts
List all available prompts
get_prompt
Get details of a specific prompt
get_server_info
Get server information and capabilities
ping
Test server connectivity

Setup

Install globally with npm: npm install -g reloaderoo, or use with npx: npx reloaderoo --help

claude_desktop_config.json
{
  "mcpServers": {
    "my-dev-server": {
      "command": "reloaderoo",
      "args": [
        "proxy",
        "--",
        "node",
        "my-dev-server.js"
      ]
    }
  }
}

Fit and risk

Best for

  • Developers
  • AI agents
  • CI/CD pipelines

Not for

  • Production environments
  • Testing stateful servers (CLI mode)

Required permissions

  • Requires filesystem access to spawn child processes
  • Requires network capability for proxy mode

Risks and side effects

  • Proxy mode may increase attack surface; ensure network security
  • CLI mode is unsuitable for stateful servers and may cause state loss

Troubleshooting

  1. Server won't start: verify child command is correct
  2. Connection issues: use --log-level debug to enable debug logging
  3. CLI command failures: run `reloaderoo inspect ping` first to test basic connectivity

Use cases

Test and debug MCP servers without configuring an MCP client
Hot-reload MCP servers during development while keeping AI sessions intact
Quickly call tools and inspect server status via CLI commands
Integrate into CI/CD pipelines for automated testing of MCP servers

Supported clients

VSCodeFull support
CursorFull support
Claude CodePartial support
WindsurfPartial support