Pyscn vs JCodemunch MCP
A side-by-side look at the Pyscn and JCodemunch MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Pyscn for developer tools work as a local process; choose JCodemunch MCP 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 Pyscn when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Choose JCodemunch MCP 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 48/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,096 | 2,803 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Pyscn | View JCodemunch MCP |
Tools & capabilities
Pyscn tools
No tool names declared yet. Check the project README from the listing page.
JCodemunch MCP 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.
Pyscn
{
"mcpServers": {
"pyscn": {
"command": "uvx",
"args": [
"pyscn@latest"
]
}
}
}
JCodemunch MCP
{
"mcpServers": {
"jcodemunch-mcp": {
"command": "uvx",
"args": [
"jcodemunch-mcp"
]
}
}
}
Frequently asked questions
Pyscn is categorized under Developer Tools and uses a local stdio subprocess. JCodemunch MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Pyscn for developer tools work and JCodemunch MCP 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.
Pyscn has no declared pricing — check the project's own site. JCodemunch MCP has no declared pricing — check the project's own site. 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 pyscn and jcodemunch-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Pyscn has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 1,096 GitHub stars. JCodemunch MCP has 49/100 (Fair) with 0 views, 0 installs and 2,803 GitHub stars.