Cortex RMCP vs World Monitor
A side-by-side look at the Cortex RMCP and World Monitor MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cortex RMCP for monitoring work as a local process; choose World Monitor for monitoring. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Cortex RMCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
Choose World Monitor when
- You need dedicated capabilities in the Monitoring domain.
- Its auth model fits you: other.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 44/100 · Fair | 45/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 89,354 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Cortex RMCP | View World Monitor |
Tools & capabilities
Cortex RMCP tools
No tool names declared yet. Check the project README from the listing page.
World Monitor tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Cortex RMCP
{
"mcpServers": {
"cortex-rmcp": {
"command": "npx",
"args": [
"-y",
"@dinglebear/cortex"
]
}
}
}
World Monitor
No confirmed install command for World Monitor yet — follow the setup steps linked from its listing page rather than a guessed package name.