panel-review MCP server — deployment

Adversarial multi-model review via OpenRouter, callable from Claude as a custom connector.

Tested before packaging: server starts, serves /mcp over streamable-http, all five tools register, and the health check reports cleanly when the API key is absent rather than crashing.

Files

Related MCP server: Zen MCP Server

Deploy

1. Put all four files in a GitHub repo, at the top level (not in a subfolder).

2. Railway → New Project → Deploy from GitHub repo → pick the repo.

3. Railway service → Variables → New Variable: OPENROUTER_API_KEY = your key. Do this before worrying about the first deploy failing.

4. Railway service → Settings → Networking → Generate Domain. Without this the service runs but has no public URL. Port 8000 if asked.

5. Your connector URL is https://<the-domain-railway-gave-you>/mcp — note the /mcp.

Connect to Claude

Customize > Connectors > + > Add custom connector, paste the URL, Add. Then enable it per conversation via the + button > Connectors.

First thing to run

Ask Claude to run panel_health. It confirms the server is reachable and the key is set. Then panel_models with a filter (deepseek, gemini, gpt) to get slugs that currently resolve — the defaults in the file will drift and should not be trusted.

Optional environment variables

Two things to know

Spend exposure. This endpoint spends your OpenRouter key and the URL is the only thing protecting it. Anyone who learns the URL can burn credits. The caps above limit the damage but do not prevent it. Set a spend limit in the OpenRouter dashboard as well, and treat the URL as a secret. If it leaks, delete the Railway domain and generate a new one.

Job state is in memory. panel_submit and panel_status share state within one process. A redeploy loses running jobs, and if you ever scale to more than one replica the poll can land on the wrong instance and report "unknown". Stay on a single replica.