Skip to content

inspector

See exactly what the model saw

An open-source debugger for MCP servers: invoke tools, read raw JSON-RPC, browse resources, test prompts and preview widgets. Run it hosted, local, or self-hosted with Docker.

Our open source tools are used by developers at top companies

NorthwindApertureCogentLumenBrightpathSundialMeridianIroncladBlue HarborKestrel

How it runs

A real debugger for a real protocol

  1. 1

    Connect

    Point it at any MCP endpoint.

  2. 2

    Call

    Invoke tools with real arguments.

  3. 3

    Read

    Every frame, in and out.

  4. 4

    Fix

    Replay the call after each change.

Protocol-level logging

Timestamped JSON-RPC frames you can expand, copy and diff between runs.

Cloud Inspectorsession #4f2a

San Francisco, CA

72°F

Partly cloudy · H 74° L 58°

now72°
2pm74°
3pm73°
4pm70°
5pm66°
6pm63°

tools/call

{
  "name": "display_weather",
  "arguments": { "city": "San Francisco" }
}

result20041ms

{ "content": [{ "type": "resource" }] }

GPT-5.2

18/18

Claude

18/18

Gemini

17/18

Widget preview

Render interactive views exactly as the host client will, with host APIs emulated.

acme-mcp · zsh

npx create-mcpfy-app

✓ tools/chart-sales.ts

✓ widgets/Chart.tsx

✓ mcpfy.config.ts

mcpfy dev

ready on :4141 · 6 tools registered

tools/chart-sales.ts

export const chartSales = tool({
  name: "chart_sales",
  input: z.object({ period: z.string() }),
});

Runs anywhere

Use it hosted, from the CLI against localhost, or self-hosted behind your own network.

Deploymentsauto · on push
  • mainProduction12s
  • feat/chartsPreview9s
  • fix/authPreview11s

npx mcpfy deploy

✓ live → my-server.mcpfy.ai/mcp

In the box

Everything you need to debug MCP

1

Tool testing

Arbitrary arguments, instant results.

2

Resource browsing

Inspect what you actually expose.

3

Prompt testing

Exercise prompts in isolation.

4

Open source

MIT licensed and self-hostable.

Debug your MCP server properly