MCPProxyRequired-tool preflights
Check local eligibility before starting a job. Get structured reasons for missing, changed, or unavailable tools.
Features / CLI & automation
Turn tool calls into repeatable workflows.
Check required tools, orchestrate calls in JavaScript or TypeScript, and operate the proxy from your terminal.
Why it matters
More intention.
Less guesswork.
An unattended job needs more than a successful connection. It needs the expected tools, the right permissions, and clear reasons when something is unavailable.
Code execution
Opt into sandboxed JavaScript or TypeScript orchestration to chain calls and transform outputs.
Stored scripts
Run reusable scripts by name instead of resending source each time.
Powerful CLI
Manage servers, inspect activity, run security checks, and integrate structured output into your workflow.
An example workflow
Check the prerequisites before an unattended job.
- Declare the tools your workflow requires.
- Run a preflight to check local eligibility and inspect failure reasons.
- Run your stored JS/TS workflow with code execution enabled.
Where the boundary is
Preflight reads local state without calling upstreams; it cannot guarantee the next call succeeds. Code execution is opt-in and its sandbox is separate from server Docker isolation.
Explore the rest of your setup