Wasmagent Js vs Edict
A side-by-side look at the Wasmagent Js and Edict 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 Edict 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 Edict when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
edict_schema, edict_version, edict_examples.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Code Execution | Code Execution |
| Quality signal | 35/100 · Fair | 63/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
Tools & capabilities
Wasmagent Js tools
No tool names declared yet. Check the project README from the listing page.
Edict tools 22
edict_schemaReturns the full AST JSON Schema — the spec for how to write programsedict_versionReturns compiler version and capability infoedict_examplesReturns 41 example programs as JSON ASTs (includes schema snippet)edict_validateValidates AST structure (field names, types, node kinds)edict_checkFull pipeline: validate → resolve names → type check → effect check → verify contractsedict_compileCompiles a checked AST to WASM (returns base64-encoded binary)edict_runExecutes a compiled WASM binary, returns output and exit codeedict_patchApplies targeted AST patches by nodeId and re-checksedict_errorsReturns machine-readable catalog of all error typesedict_lintRuns non-blocking quality analysis and returns warningsedict_debugExecution tracing and crash diagnosticsedict_composeCombines composable program fragments into a module- +10 more on 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.
Edict
{
"mcpServers": {
"sowiedu-edict": {
"command": "npx",
"args": [
"-y",
"edict-lang"
]
}
}
}
Frequently asked questions
Wasmagent Js is categorized under Code Execution and uses an install path we have not confirmed yet. Edict belongs to Code Execution and uses a local stdio subprocess. Pick Wasmagent Js for code execution work and Edict 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. Edict is listed as free. Auth: no auth required. 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 sowiedu-edict 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. Edict has 63/100 (Good) with 2 views, 0 installs and 12 GitHub stars.
