Magic MCP vs PDFMonkey
A side-by-side look at the Magic MCP and PDFMonkey MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Magic MCP for developer tools work as a local process; choose PDFMonkey 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 Magic MCP 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:
TWENTY_FIRST_API_KEY, API_KEY_21ST.
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 | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 53/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Paid service | BYOK (pay the provider) |
| Required env vars | TWENTY_FIRST_API_KEYAPI_KEY_21ST |
Tools & capabilities
Magic MCP tools
No tool names declared yet. Check the project README from the listing page.
PDFMonkey tools 11
list_workspaceslist_templatesget_templategenerate_documentget_document_statuslist_documentsdelete_documentlist_snippetsget_snippetget_quotaget_user_info
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.
Magic MCP
{
"mcpServers": {
"21st-dev-magic-mcp": {
"command": "npx",
"args": [
"-y",
"@21st-dev/cli@latest"
],
"env": {
"TWENTY_FIRST_API_KEY": "YOUR_TWENTY_FIRST_API_KEY_HERE",
"API_KEY_21ST": "YOUR_API_KEY_21ST_HERE"
}
}
}
}
PDFMonkey
{
"mcpServers": {
"pdfmonkey": {
"command": "npx",
"args": [
"-y",
"pdfmonkey-mcp-server"
],
"env": {
"PDFMONKEY_API_KEY": "YOUR_PDFMONKEY_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Magic MCP is categorized under Developer Tools and uses a local stdio subprocess. PDFMonkey belongs to Developer Tools and uses a local stdio subprocess. Pick Magic MCP for developer tools work and PDFMonkey 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.
Magic MCP is listed as a paid service. Auth: api key required. PDFMonkey is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 21st-dev-magic-mcp and pdfmonkey as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Magic MCP has a quality signal of 53/100 (Good) with 16 views, 1 installs and 5,997 GitHub stars. PDFMonkey has 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
