MCP Server Testing Suite

This skill provides two testing modes for MCP servers, both powered by @mcp-use/inspector.

How it works

The inspector runs a local web server that proxies JSON-RPC requests to your MCP server. Every MCP operation (initialize, tools/list, tools/call, resources/list, prompts/get, etc.) goes through curl calls to the inspector's API. This means you can test any MCP server reachable over HTTP/SSE or WebSocket without needing a config file or daemon.

Command: /mcp-test

Basic protocol-level testing. Verifies every MCP primitive works correctly.

When the user invokes /mcp-test, follow the guide in references/basic-test-guide.md. This command:

1. Asks the user for their MCP server URL (or detects it from context)
2. Starts the inspector in the background
3. Runs through every MCP primitive systematically
4. Reports pass/fail for each check
5. Cleans up the inspector process