PDFMonkey vs .prompts
A side-by-side look at the PDFMonkey and .prompts MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
.
.promptsDeveloper Tools.prompts, the home to all your AI prompts, everywhere you need them.38FairAuth: not declaredVerdict: choose PDFMonkey for developer tools work as a local process; choose .prompts for developer tools. 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | . .prompts | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 49/100 · Fair | 38/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | PDFMONKEY_API_KEY | None listed |
| Verified owner |
Tools & capabilities
PDFMonkey tools 11
list_workspaceslist_templatesget_templategenerate_documentget_document_statuslist_documentsdelete_documentlist_snippetsget_snippetget_quotaget_user_info
.prompts 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"
}
}
}
}
.prompts
No confirmed install command for .prompts yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
PDFMonkey is categorized under Developer Tools and uses a local stdio subprocess. .prompts belongs to Developer Tools and uses an install path we have not confirmed yet. Pick PDFMonkey for developer tools work and .prompts 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. .prompts has no confirmed install command yet — follow its own setup instructions.
PDFMonkey is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. .prompts 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 pdfmonkey and prompts 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. .prompts has 38/100 (Fair) with 5 views, 0 installs and 0 GitHub stars.