PDFMonkey vs Docker MCP
A side-by-side look at the PDFMonkey and Docker MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose PDFMonkey for developer tools work as a local process; choose Docker 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 PDFMonkey when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
PDFMONKEY_API_KEY. - You want tools like
list_workspaces, list_templates, get_template.
Choose Docker 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 | 49/100 · Fair | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | PDFMONKEY_API_KEY | None listed |
Tools & capabilities
PDFMonkey tools 11
list_workspaceslist_templatesget_templategenerate_documentget_document_statuslist_documentsdelete_documentlist_snippetsget_snippetget_quotaget_user_info
Docker 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.
PDFMonkey
{
"mcpServers": {
"pdfmonkey": {
"command": "npx",
"args": [
"-y",
"pdfmonkey-mcp-server"
],
"env": {
"PDFMONKEY_API_KEY": "YOUR_PDFMONKEY_API_KEY_HERE"
}
}
}
}
Docker MCP
{
"mcpServers": {
"quantgeekdev-docker-mcp": {
"command": "uvx",
"args": [
"docker-mcp"
]
}
}
}
Frequently asked questions
PDFMonkey is categorized under Developer Tools and uses a local stdio subprocess. Docker MCP belongs to Developer Tools and uses a local stdio subprocess. Pick PDFMonkey for developer tools work and Docker 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.
PDFMonkey is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Docker MCP 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 pdfmonkey and quantgeekdev-docker-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, PDFMonkey has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Docker MCP has 43/100 (Fair) with 4 views, 0 installs and 505 GitHub stars.
