Love the hosted SSE/HTTP mirrors and registry. We built something similar to catch handshake drift in our remote MCP clients, and being able to replay the JSON-RPC log in-browser saved us from chasing environment-specific timeouts because we could rerun the exact frame sequence from the failure. One idea: add a little health badge per server showing last-seen transport (HTTP/SSE/WS) plus a running error count so integrators know which endpoint matches their stack before they flip the switch.
Really appreciate this — handshake drift is a real issue in MCP setups. Also love the health badge idea (showing last transport + error count would be super helpful).
Inspector is the right tool for local STDIO servers — use it. We're complementary, not competing.
MCP Playground fills a different gap: no install (browser tab, nothing to run), built for remote HTTP/SSE endpoints rather than local processes, and includes hosted test servers so you can verify your client implementation without needing a server at all. Plus a registry if you're trying to discover what's out there.
Inspector ideal for: STDIO, local debugging, open source, deeper protocol introspection.
MCP Playground for: zero setup, remote servers, client testing, browsing mcp registry/server list.
Love the hosted SSE/HTTP mirrors and registry. We built something similar to catch handshake drift in our remote MCP clients, and being able to replay the JSON-RPC log in-browser saved us from chasing environment-specific timeouts because we could rerun the exact frame sequence from the failure. One idea: add a little health badge per server showing last-seen transport (HTTP/SSE/WS) plus a running error count so integrators know which endpoint matches their stack before they flip the switch.
Really appreciate this — handshake drift is a real issue in MCP setups. Also love the health badge idea (showing last transport + error count would be super helpful).
Thanks for sharing
Any plan to support ws transport ? A few newer mcp servers are moving away from SSE
yes, it’s in the pipeline.
I liked the recipe part though especially the Meta Ads one, you can keep it open for others to contribute as well—it could help increase engagement.
Noted. Thanks
How is this different from MCP Inspector?
Inspector is the right tool for local STDIO servers — use it. We're complementary, not competing.
MCP Playground fills a different gap: no install (browser tab, nothing to run), built for remote HTTP/SSE endpoints rather than local processes, and includes hosted test servers so you can verify your client implementation without needing a server at all. Plus a registry if you're trying to discover what's out there.
Inspector ideal for: STDIO, local debugging, open source, deeper protocol introspection. MCP Playground for: zero setup, remote servers, client testing, browsing mcp registry/server list.
Add a dark mode
Noted. Thanks for the feedback.