Overview
Thesunpeak inspect command connects to any MCP server and launches the inspector — no sunpeak project required. Use it to test and debug MCP servers built with any language or framework.
Options
Examples
How It Works
- Connects to the MCP server via HTTP/SSE or stdio transport
- Discovers tools and resources via MCP protocol (
tools/list,resources/list) - Builds simulations from discovered tools, optionally merging JSON fixtures from
--simulations - Launches the multi-host inspector UI (Vite dev server)
- Proxies tool calls and resource reads through to the connected server
Transport Support
- HTTP/SSE: URLs starting with
http://orhttps://connect via Streamable HTTP transport - Stdio: Any other string is parsed as a shell command and connects via stdio transport (e.g.,
"python my_server.py","node server.js")
Authentication
sunpeak auto-negotiates MCP OAuth when the server returns 401 Unauthorized and publishes standard MCP OAuth metadata. If you already have a token, pass it as an HTTP header:--header for other HTTP auth schemes or tenant headers.
Combining with Simulations
Use--simulations to overlay mock data on discovered tools. This lets you test specific states without modifying your server:
Related Commands
sunpeak dev
Full dev server with built-in inspector for sunpeak projects.
Inspector
Inspector concepts and features.