N8n MCP vs PDF Reader MCP
A side-by-side look at the N8n MCP and PDF Reader MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose N8n MCP for developer tools work as a local process; choose PDF Reader 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 N8n MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
N8N_API_URL, N8N_API_KEY, N8N_MCP_READ_ONLY, N8N_MCP_DISABLED_TOOLS, N8N_MCP_ALLOWED_WORKFLOW_IDS, N8N_MCP_ALLOWED_TAGS. - You want tools like
node_scaffold, workflow_generate, workflow_lint.
Choose PDF Reader MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
inspect, outline, read.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 60/100 · Good | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | N8N_API_URLN8N_API_KEYN8N_MCP_READ_ONLYN8N_MCP_DISABLED_TOOLSN8N_MCP_ALLOWED_WORKFLOW_IDSN8N_MCP_ALLOWED_TAGS |
Tools & capabilities
N8n MCP tools 12
node_scaffoldScaffold a TypeScript skeleton for an n8n custom node from a plain-English description. Returns a single TypeScript file implementing INodeType with description, credentials reference, and an execute method stub. Pure code generation — no network, no filesystem writes.workflow_generateGenerate a valid n8n workflow JSON from a plain-English description. Handles webhook/schedule/RSS triggers, common action nodes (Slack, Google Sheets, Discord, Gmail, Notion, HTTP), and AI Agent setups (LangChain root agent + chat model + memory + optional HTTP tool, wired with ai_languageModel / ai_memory / ai_tool connections). Returns workflow JSON with unique node IDs, connections, positions, and typeVersion on every node. Output is non-deterministic (random node IDs and webhook paths).workflow_lintLint an n8n workflow JSON. Returns concrete errors and warnings: missing credentials, deprecated node types (Function -> Code, spreadsheetFile -> convertToFile/extractFromFile), broken connections, missing or non-numeric typeVersion, duplicate node names or IDs, AI Agent missing ai_languageModel sub-node, Webhook missing webhookId, IF node still on v1 condition schema, rate-sensitive nodes without retries, Code-node sandbox violations, expression staleness (`$('NodeName')` referencing missing nodes), manualTrigger in active workflows, disabled-but-wired nodes, empty Set nodes, HTTP method/body mismatches, Schedule trigger DST risk, credential drift, webhook test paths in active workflows. Deterministic, rule-based.workflow_diffSemantic diff between two workflows. Reports nodes added / removed / modified (with field-level deltas: type, typeVersion, parameters, credentials, disabled, position), connection topology changes, and settings drift. Ignores noise (small position deltas, createdAt/updatedAt). Pair with workflow_get to compare deployed vs local. Deterministic.execution_explainDiagnose a failed or surprising n8n execution. Paste the execution JSON (from the n8n UI 'Show details' or `GET /executions/:id?includeData=true`); returns a per-node summary highlighting nodes that returned 0 items, unresolved `={{ ... }}` expressions, errors with hints, and LLM token usage. Hits the most common debugging pain point: items 'silently disappearing' between nodes. Deterministic, rule-based.
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.
N8n MCP
{
"mcpServers": {
"n8n-mcp": {
"command": "npx",
"args": [
"-y",
"@automatelab/n8n-mcp"
],
"env": {
"N8N_API_URL": "YOUR_N8N_API_URL_HERE",
"N8N_API_KEY": "YOUR_N8N_API_KEY_HERE",
"N8N_MCP_READ_ONLY": "YOUR_N8N_MCP_READ_ONLY_HERE",
"N8N_MCP_DISABLED_TOOLS": "YOUR_N8N_MCP_DISABLED_TOOLS_HERE",
"N8N_MCP_ALLOWED_WORKFLOW_IDS": "YOUR_N8N_MCP_ALLOWED_WORKFLOW_IDS_HERE",
"N8N_MCP_ALLOWED_TAGS": "YOUR_N8N_MCP_ALLOWED_TAGS_HERE"
}
}
}
}
PDF Reader MCP
{
"mcpServers": {
"pdf-reader-mcp": {
"command": "npx",
"args": [
"-y",
"@sylphx/anymd"
]
}
}
}
Frequently asked questions
N8n MCP is categorized under Developer Tools and uses a local stdio subprocess. PDF Reader MCP belongs to Developer Tools and uses a local stdio subprocess. Pick N8n MCP for developer tools work and PDF Reader 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.
N8n MCP has no declared pricing — check the project's own site. PDF Reader MCP 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 n8n-mcp and pdf-reader-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, N8n MCP has a quality signal of 60/100 (Good) with 2 views, 0 installs and 14 GitHub stars. PDF Reader MCP has 69/100 (Great) with 2 views, 0 installs and 1,040 GitHub stars.