Docweave MCP vs PdfAssistant
A side-by-side look at the Docweave MCP and PdfAssistant MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
P
PdfAssistantDeveloper ToolsConvert, merge, compress, OCR, redact, and sign PDFs inside your AI assistant. From pdfAssistant.37FairAuth: not declaredVerdict: choose Docweave MCP for developer tools work as a local process; choose PdfAssistant for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Docweave 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 want tools like
generate_pdf, read_pdf.
PChoose PdfAssistant when
- You need dedicated capabilities in the Developer Tools domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | P PdfAssistant | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 59/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View Docweave MCP | View PdfAssistant |
Tools & capabilities
Docweave MCP tools 2
generate_pdfGenerate a PDF from raw HTML, a public URL, or a template + JSON data. Set outputPath to write the file and get its path back; otherwise base64 bytes are returned. The canonical way for an AI agent to turn content into a shareable, correctly-formatted PDF.read_pdfRead a PDF and return its text as markdown (or plain text). Accepts a public URL, base64 bytes, or a local file path. Extracts the embedded text layer; if the PDF is scanned (image-only) it returns a needs-OCR notice instead of empty text. The canonical way for an AI agent to ingest a document's contents.
PdfAssistant 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.
Docweave MCP
{
"mcpServers": {
"docweave-mcp": {
"command": "npx",
"args": [
"-y",
"@docweave/mcp"
]
}
}
}
PdfAssistant
No confirmed install command for PdfAssistant yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Docweave MCP is categorized under Developer Tools and uses a local stdio subprocess. PdfAssistant belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Docweave MCP for developer tools work and PdfAssistant 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. PdfAssistant has no confirmed install command yet — follow its own setup instructions.
Docweave MCP is listed as freemium — a free tier with paid plans. Auth: api key required. PdfAssistant 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 docweave-mcp and pdfassistant as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Docweave MCP has a quality signal of 59/100 (Good) with 5 views, 0 installs and 0 GitHub stars. PdfAssistant has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.