MCP Debugger vs PaperDock
A side-by-side look at the MCP Debugger and PaperDock MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
P
PaperDockDeveloper ToolsCreate, edit, and review LaTeX with AI agents in PaperDock, an independent alternative to Overleaf.38FairAuth: not declaredVerdict: choose MCP Debugger for developer tools work as a local process; choose PaperDock for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Debugger when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
PChoose PaperDock when
- You need dedicated capabilities in the Developer Tools domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | P PaperDock | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 51/100 · Good | 38/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| 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 | 179 | — |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCP Debugger | View PaperDock |
Tools & capabilities
MCP Debugger tools
No tool names declared yet. Check the project README from the listing page.
PaperDock 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 Debugger
{
"mcpServers": {
"mcp-debugger-2": {
"command": "npx",
"args": [
"-y",
"@debugmcp/mcp-debugger"
]
}
}
}
PaperDock
No confirmed install command for PaperDock yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
MCP Debugger is categorized under Developer Tools and uses a local stdio subprocess. PaperDock belongs to Developer Tools and uses an install path we have not confirmed yet. Pick MCP Debugger for developer tools work and PaperDock 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. PaperDock has no confirmed install command yet — follow its own setup instructions.
MCP Debugger has no declared pricing — check the project's own site. PaperDock 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-debugger-2 and paperdock as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Debugger has a quality signal of 51/100 (Good) with 2 views, 0 installs and 179 GitHub stars. PaperDock has 38/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.