📖 TL;DR

Go to MCP Playground → Test MCP Server — it's free, no sign-up
Paste your server URL, add a Bearer token if required, click Connect
Browse tools, prompts, and resources; execute tools with custom arguments
Use the JSON-RPC log to debug protocol-level issues
Works with HTTP + SSE and Streamable HTTP transports; not STDIO servers

If you've been building with MCP, you know the iteration loop can be slow. Write server code → restart the server → open Claude Desktop → restart Claude Desktop → ask a question → see if the tool got called → repeat. When something goes wrong, it's not obvious where the failure happened.

MCP Playground breaks this loop. It's a browser-based MCP client that connects directly to any remote server, shows you everything the server exposes, lets you call tools with custom arguments, and displays the raw JSON-RPC traffic — all without touching your local config.

What You Can Test

🔧 Tools

Call any tool with custom arguments and see the raw response. Great for validating schemas and testing error handling.

💬 Prompts

Fetch prompt templates and test them with real argument values before embedding them in your app.

📁 Resources

Browse and read server resources — database records, files, or API data exposed as structured content.

📡 Protocol Logs

View every JSON-RPC message in real time — initialize, capabilities, tool calls, and responses.

Step-by-Step: Testing a Remote MCP Server

Step 1 — Open the tester

Go to mcpplaygroundonline.com/mcp-test-server. No account, no install. The interface loads instantly in your browser.

Step 2 — Enter the server URL

Paste the remote server URL into the input field. URLs typically end in /sse (SSE transport) or /mcp (Streamable HTTP). Examples:

https://mcp.supabase.com/sse
https://api.githubcopilot.com/mcp
https://your-server.com/mcp/sse

Step 3 — Add authentication (if required)

If the server requires authentication, expand the auth section and paste your Bearer token. The token is sent as an Authorization: Bearer <token> header on all requests — it's never stored on our servers.

⚠️ Use test tokens

Avoid pasting production credentials. For testing, create a read-only API key or a token scoped to only the permissions needed for the test.

Step 4 — Click Connect

MCP Playground sends the initialize handshake, negotiates protocol version and capabilities, then calls tools/list, prompts/list, and resources/list. Within a second or two you'll see the server's capabilities appear in the panel.

Step 5 — Explore and execute

Click any tool to expand its schema — you'll see the input parameters, their types, and descriptions. Fill in the arguments and click Execute. The response appears inline with the full JSON-RPC structure, including any error details.

✅ Pro tip: check the Logs tab

The Logs tab shows every raw JSON-RPC message. If a tool call fails, the error message here is usually more precise than the high-level UI error. Look for the error.message field in the response object.

Supported Transport Types

HTTP + SSE

The original MCP transport. Client sends HTTP POST for each request; server streams responses via Server-Sent Events. URL typically ends in /sse.

✅ Supported

Streamable HTTP

The modern MCP transport (spec v2025-03-26+). Bidirectional streaming over a single HTTP connection. URL typically ends in /mcp.

✅ Supported

STDIO

Local process communication over stdin/stdout. Used by npm and PyPI packages. Cannot run in a browser context.

❌ Not supported

Debugging Common Connection Errors

Error	Likely Cause	Fix
Failed to fetch	CORS not enabled on server, or server is down	Check server is running; add `Access-Control-Allow-Origin: *` header
403 Forbidden	Missing or expired auth token	Add or refresh your Bearer token in the auth field
404 Not Found	Wrong URL path — missing /sse or /mcp suffix	Check the server docs for the exact endpoint path
Connection timeout	Server too slow to respond or initialize	Check server logs; cold-start latency on serverless deployments is common
No tools listed	Server requires auth before exposing tools/list	Add a valid API key; some servers hide tools until authenticated

Testing a Server You Built Yourself

If you're developing an MCP server locally, you'll need to expose it over a public or tunneled URL since MCP Playground runs in the browser and can't reach localhost directly.

Options:

ngrok: ngrok http 3000 — gives you a public HTTPS URL in seconds
Cloudflare Tunnel: cloudflared tunnel --url http://localhost:3000 — free, persistent option
Deploy to Vercel/Railway: push to a branch and test against the preview deployment URL

Once tunneled, paste the public URL into MCP Playground and iterate freely — no editor restart required.

Before You Add a Server to Your Config

Testing a server in MCP Playground before adding it to your editor config is a recommended practice. It lets you verify:

The server is reachable and not returning errors
Your API key or Bearer token works correctly
The tools listed match what you expect
Tool arguments are structured correctly before you waste LLM tokens on bad calls
The server doesn't expose sensitive data or overly broad permissions

You can also use the MCP Security Scanner to run an automated audit — it checks HTTPS enforcement, authentication, CORS headers, rate limiting, and 15+ other security properties in about 30 seconds.

Test Any MCP Server — Free

Connect, explore tools, and execute calls from your browser. No sign-up, no install.

Test MCP Server → Run Security Scan

Related Resources

MCP Config Generator — generate client configs from a URL or package name
MCP Security Scanner — 20+ automated security checks for your server
MCP Servers Directory — browse 1,000+ servers to find one to test
Complete Guide to MCP Config Files — Claude Desktop, Cursor, Lovable, Zed and more
Build a Custom MCP Server — step-by-step Node.js guide