@docweave/mcp
Related Servers
Alternatives to @docweave/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools for reading, writing, and manipulating PDF files, including text extraction, metadata retrieval, and merging or splitting documents. It also enables users to create PDFs from plain text and convert specific pages or entire documents into images.37 npmISC
- FlicenseNot gradedqualityDmaintenanceMCP server for extracting text from PDF files, supporting local files and URLs.-
- AlicenseAqualityBmaintenanceRust-powered PDF toolkit over MCP: create, read, and analyze PDFs; extract text and entities for RAG; convert to Markdown; split/merge/rotate/reorder pages; manage form fields and annotations; encrypt documents. Runs locally via uvx oxidize-mcp.125MIT
- AlicenseNot gradedqualityCmaintenanceA local MCP server that drives PDFium and pypdf to perform comprehensive PDF operations including inspection, assembly, page editing, watermarking, rendering, extraction, form filling, encryption, compression, attachments, bookmarks, and metadata management.MIT
- AlicenseAqualityAmaintenanceMCP server that converts HTML or Markdown to PDF and can generate PDFs from URLs, with tools generate_pdf and pdf_from_url.21MIT
- AlicenseAqualityCmaintenanceProvides PDF reading, text search, navigation, and form filling capabilities through MCP, with cross-platform PDF viewer integration for seamless document interaction.79MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or confusion between tools. The single tool has a clear, distinct purpose.
The tool name 'generate_pdf' follows a clear verb_noun pattern. With only one tool, consistency is perfect and the name is descriptive.
A single tool suggests a very narrow scope. While PDF generation is a specific task, the server might benefit from additional related tools (e.g., listing templates or managing output) to feel more complete. The count is borderline thin.
The tool covers multiple input types (HTML, URL, template+data) and options (file path or bytes). However, there is no management of templates or output files, and no other lifecycle operations, leaving notable gaps for a full document workflow.