mcp-test s

This MCP server collection provides a comprehensive suite of test servers that implement the Model Context Protocol (MCP). The recommended entry point is the everything server, which exercises a wide range of MCP features through tools, resources, prompts, elicitation, dynamic tools, roots echo, and environment variable handling. You can start any server directly via npx, e.g., npx @msfeldstein/mcp-test-servers everything, and Cursor can query and validate the server’s behavior using the included tools and prompts. The repository presents many example servers (e.g., ping, elicitation, prompts, dynamic tool management, and OAuth repros) that demonstrate how MCP handlers should respond to parameter validation, structured content, prompts, and root operations. Use the everything server to run automated tests, explore tool outputs, and verify MCP compatibility across scenarios.

Prerequisites:

• Node.js installed (npx is included with Node.js)
• Access to the npm registry (public internet)

Step-by-step:

1. Ensure Node.js and npm are installed. You can verify with: node -v npm -v

2. Run the server container or local install via npx (no local install required): npx -y @msfeldstein/mcp-test-servers everything

3. If you want to use a specific server from the collection, replace everything with the server name, for example: npx -y @msfeldstein/mcp-test-servers ping

4. For development or integration, you can also examine the repository structure to see available servers and their configurations, as well as how CLI usage maps to MCP requests.

Notes:

• The commands shown rely on the package publishing environment and may require network access to fetch the package on first run.
• You can capture environment variables by configuring an env block when using a programmatic MCP launcher.

Tips and common considerations:

• The everything server is designed to exercise MCP features end-to-end; use it to validate parameter handling, elicitation flows, root echo functionality, and dynamic tool behavior.
• If you encounter validation errors, check the tool schemas (type, anyOf/allOf/oneOf usage) and ensure your MCP client is sending compatible payloads.
• Environment variables can influence server behavior (e.g., named servers or long-running tests). Use the env block in the mcp_config or pass appropriate environment values in your runtime.
• Some servers simulate OAuth flows or complex interactions; for those, ensure the correct ports and endpoints are accessible if you’re testing in a local environment.
• When debugging, start the specific server (e.g., ping) to isolate behavior before running the entire everything suite.