Jshookmcp vs Warmplane
A side-by-side look at the Jshookmcp and Warmplane MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Jshookmcp for developer tools work as a local process; choose Warmplane for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Jshookmcp when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Warmplane when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 53/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,060 | 5 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Jshookmcp | View Warmplane |
Tools & capabilities
Jshookmcp tools
No tool names declared yet. Check the project README from the listing page.
Warmplane 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.
Jshookmcp
{
"mcpServers": {
"jshookmcp": {
"command": "npx",
"args": [
"-y",
"@jshookmcp/jshook@latest"
]
}
}
}
Warmplane
{
"mcpServers": {
"warmplane": {
"command": "npx",
"args": [
"--arg",
"-y",
"--arg",
"@modelcontextprotocol/server-filesystem"
]
}
}
}
Frequently asked questions
Jshookmcp is categorized under Developer Tools and uses a local stdio subprocess. Warmplane belongs to Developer Tools and uses a local stdio subprocess. Pick Jshookmcp for developer tools work and Warmplane for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Jshookmcp is listed as free. Auth: no auth required. Warmplane has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add jshookmcp and warmplane as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Jshookmcp has a quality signal of 53/100 (Good) with 2 views, 0 installs and 2,060 GitHub stars. Warmplane has 43/100 (Fair) with 0 views, 0 installs and 5 GitHub stars.