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