Skip to main content

Overview

The sunpeak 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

  1. Connects to the MCP server via HTTP/SSE or stdio transport
  2. Discovers tools and resources via MCP protocol (tools/list, resources/list)
  3. Builds simulations from discovered tools, optionally merging JSON fixtures from --simulations
  4. Launches the multi-host inspector UI (Vite dev server)
  5. Proxies tool calls and resource reads through to the connected server

Transport Support

  • HTTP/SSE: URLs starting with http:// or https:// 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:
You can repeat --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:
Simulation JSON files in the directory are matched to tools by filename. See Simulation API Reference for the JSON schema.

sunpeak dev

Full dev server with built-in inspector for sunpeak projects.

Inspector

Inspector concepts and features.