What deployment platforms are supported?
Frontend on Vercel, backend on Render or Heroku.
@rikki-codes
Basic information
A web app to test MCP servers using an installation code from Smithery.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"mcp-server-test-app": {
"command": "node",
"args": [
"index.js"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
A web app to test MCP servers using an installation code from Smithery. It accepts a code, verifies server connectivity, and displays success or error messages. Designed for developers deploying and testing MCP servers.
Clone the repository, then set up the frontend and backend separately. For the frontend: cd frontend; npm install; npm run dev. For the backend: cd backend; npm install; node index.js. Deploy the frontend on Vercel and the backend on Render or Heroku, using environment variables for security.
Frontend on Vercel, backend on Render or Heroku.
Frontend: React with TypeScript, Axios, CSS. Backend: Node.js with Express, Axios, dotenv.
Frontend: `cd frontend; npm install; npm run dev`. Backend: `cd backend; npm install; node index.js`.
Mobbin MCP connects your AI agents to 600,000+ real product screens, so what they build starts with what already works.

SSH MCP server for AI agents: remote commands, file transfer, log search and server audits through OpenSSH.

Automated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.

Know when your AI agents, cron jobs and CI pipelines fail, stall or go quiet. Your agent sets up monitors from a plain description, tells you what is broken and why, reads run history and traces, and writes notes on inci

Comments