Overview
What is MCP Server Testing Web App?
A web application that accepts an MCP server configuration in JSON format, verifies the server’s connectivity and functionality, and displays the results. It runs on a Node.js backend with a React frontend and is deployed on Vercel.
How to use MCP Server Testing Web App?
Clone the repository, install dependencies for both backend and frontend, run the backend server on http://localhost:3000, create a .env file in the frontend folder with VITE_API_URL=http://localhost:3000/check-mcp, then start the frontend with npm run dev. Input an MCP server config as JSON to test.
Key features of MCP Server Testing Web App
- Accepts MCP server configuration as JSON input
- Tests server connectivity by running the MCP server on backend
- Displays results in a user-friendly interface
- Backend implemented using Node.js and Express
- Frontend built with React
Use cases of MCP Server Testing Web App
- Validate a new MCP server configuration before deploying it
- Quickly check if a remote MCP server is reachable and provides tools
- Debug MCP server setups by inspecting connectivity and tool listings
FAQ from MCP Server Testing Web App
What does the backend do?
The backend receives the JSON config, executes the MCP server test command using spawn(command, args), connects to the MCP server via WebSockets to fetch available tools, and returns the results to the frontend.
What runtime does the app require?
Both Node.js and npm are required to run the backend and install dependencies. The frontend runs on a modern web browser.
What format should the JSON input follow?
The JSON should include an mcpServers object with server names as keys. Each server entry must have a command string and an args array. An example uses npx with the @smithery/cli package.
Where is the application deployed?
The app is deployed on Vercel.
How does the frontend communicate with the backend?
The frontend sends the MCP server config to the backend via an API request to VITE_API_URL (the /check-mcp endpoint).
