inclusio-mcp
Related Servers
Alternatives to inclusio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that renders LaTeX to PDF via pdflatex, supporting raw LaTeX and Jinja2 templates with artifact generation.11MIT
- AlicenseAqualityBmaintenanceEasyAccessPDF is a production MCP server for PDF accessibility and document conversion. Five tools: convert documents (PDF/DOCX/PPT/XLS/HTML/EPUB/RTF/ODT/TXT) to clean Markdown; export PDFs to JSON/HTML/text/annotated-PDF; run veraPDF PDF/UA-1 (ISO 14289) accessibility audits with graded reports; auto-tag and remediate PDFs for WCAG 2.1/2.2, Section 508, ADA Title II and EAA/EN 301 549 compliance.5MIT
- AlicenseBqualityDmaintenanceA universal MCP server for document processing, conversion, and automation. Handle PDF, DOCX, HTML, Markdown, and more through a unified API and toolset.1356 npm140MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for programmatic creation, modification, and compilation of structured LaTeX documents.33 npm3Apache 2.0
- AlicenseAqualityAmaintenanceMCP server for Office documents — create, edit, fill templates, convert, and extract Word/Excel/PowerPoint. LaTeX-style markup, math formulas, PDF export, template loops, and document diff. stdio / SSE / Streamable HTTP with auth and rate limiting.1222 PyPIApache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server that lets AI agents produce print-ready, typographically correct PDFs using Typst, with a page-as-canvas engine, multiple templates, and per-page layout quality control.2MIT
TDQS
Scored across 4 tools
list_docs and doc_count are the only near-overlap pair, but their descriptions clearly separate a full metadata listing from a cheap count probe. render and audit_pdf target distinct stages of the workflow with no ambiguity.
list_docs and audit_pdf follow a verb_noun pattern, but doc_count reverses the pattern and render is a bare verb without an object. The names are readable and all snake_case, but the imperative convention is not applied consistently.
Four tools is a well-scoped size for a focused document rendering and PDF auditing server. Each tool serves a distinct step or lightweight probe, and doc_count does not feel like unnecessary padding.
The set covers discovery, counting, rendering source, and auditing existing PDFs, but there is no tool to compile rendered LaTeX or Markdown into a PDF, so after render an agent cannot produce the PDF that audit_pdf expects. Document registration/update may be intentionally external, but the missing build/compile step is a significant workflow gap.