Wasmagent Js vs Parselbox
A side-by-side look at the Wasmagent Js and Parselbox MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Wasmagent Js for code execution work; choose Parselbox for code execution as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Wasmagent Js when
- You need dedicated capabilities in the Code Execution domain.
Choose Parselbox when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Code Execution | Code Execution |
| Quality signal | 35/100 · Fair | 41/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 3 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Wasmagent Js | View Parselbox |
Tools & capabilities
Wasmagent Js tools
No tool names declared yet. Check the project README from the listing page.
Parselbox 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.
Wasmagent Js
No confirmed install command for Wasmagent Js yet — follow the setup steps linked from its listing page rather than a guessed package name.
Parselbox
{
"mcpServers": {
"parselbox": {
"command": "uvx",
"args": [
"parselbox"
]
}
}
}
Frequently asked questions
Wasmagent Js is categorized under Code Execution and uses an install path we have not confirmed yet. Parselbox belongs to Code Execution and uses a local stdio subprocess. Pick Wasmagent Js for code execution work and Parselbox for code execution.
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. Wasmagent Js has no confirmed install command yet — follow its own setup instructions.
Wasmagent Js has no declared pricing — check the project's own site. Parselbox 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 mcp-server-163 and parselbox as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Wasmagent Js has a quality signal of 35/100 (Fair) with 0 views, 0 installs and 6 GitHub stars. Parselbox has 41/100 (Fair) with 0 views, 0 installs and 3 GitHub stars.
