Bomly vs Jshookmcp
A side-by-side look at the Bomly and Jshookmcp MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Bomly for developer tools work as a local process; choose Jshookmcp 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 Bomly 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 Jshookmcp 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 | 48/100 · Fair | 52/100 · Good |
| 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 | 14 | 2,060 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Bomly | View Jshookmcp |
Tools & capabilities
Bomly tools
No tool names declared yet. Check the project README from the listing page.
Jshookmcp 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.
Bomly
{
"mcpServers": {
"bomly": {
"command": "npx",
"args": [
"-y",
"bomly-mcp"
]
}
}
}
Jshookmcp
{
"mcpServers": {
"jshookmcp": {
"command": "npx",
"args": [
"-y",
"@jshookmcp/jshook@latest"
]
}
}
}
Frequently asked questions
Bomly is categorized under Developer Tools and uses a local stdio subprocess. Jshookmcp belongs to Developer Tools and uses a local stdio subprocess. Pick Bomly for developer tools work and Jshookmcp 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.
Bomly is listed as free. Auth: no auth required. Jshookmcp 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 bomly and jshookmcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Bomly has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 14 GitHub stars. Jshookmcp has 52/100 (Good) with 2 views, 0 installs and 2,060 GitHub stars.