Hot-reload monitor for MCP servers - like nodemon but for Model Context Protocol
Hot-reload monitor for MCP servers - like nodemon but for Model Context Protocol
Make changes to your MCP server code and see them instantly without restarting your MCP client. Just like nodemon automatically restarts Node.js applications, mcpmon automatically restarts MCP servers.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
{
"mcpServers": {
"my-server": {
"command": "mcpmon",
"args": [
"node",
"server.js"
],
"env": {
"API_KEY": "YOUR_API_KEY"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| API_KEY | Declared in the maintainer’s client configuration. | Check documentation |
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Person-owned, portable AI memory as a remote MCP server, readable and writable by any MCP client.
A knowledge base of verified, dated facts your LLM would otherwise get wrong.
A simple MCP server of knowledge base for RAGFlow.
Two-layer memory MCP server for AI agents with 37 tools, RAG, graphs, wiki, auth