MCP Doctor vs Pyscn
A side-by-side look at the MCP Doctor 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 MCP Doctor 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 MCP Doctor when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OPENAI_API_KEY, OPENAI_BASE_URL, MCP_DOCTOR_MODEL.
Choose Pyscn 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 | 37/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 | Free |
| Required env vars | OPENAI_API_KEYOPENAI_BASE_URLMCP_DOCTOR_MODEL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 1,096 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCP Doctor | View Pyscn |
Tools & capabilities
MCP Doctor 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.
MCP Doctor
{
"mcpServers": {
"mcp-doctor": {
"command": "uvx",
"args": [
"mcp-doctor"
],
"env": {
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"OPENAI_BASE_URL": "YOUR_OPENAI_BASE_URL_HERE",
"MCP_DOCTOR_MODEL": "YOUR_MCP_DOCTOR_MODEL_HERE"
}
}
}
}
Pyscn
{
"mcpServers": {
"pyscn": {
"command": "uvx",
"args": [
"pyscn-mcp"
]
}
}
}
Frequently asked questions
MCP Doctor is categorized under Developer Tools and uses a local stdio subprocess. Pyscn belongs to Developer Tools and uses a local stdio subprocess. Pick MCP Doctor 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.
MCP Doctor has no declared pricing — check the project's own site. Pyscn 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-doctor and pyscn as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Doctor has a quality signal of 37/100 (Fair) with 4 views, 0 installs and 1 GitHub stars. Pyscn has 49/100 (Fair) with 1 views, 0 installs and 1,096 GitHub stars.