F
licenseNot graded
qualityC
maintenanceEnables AI agents to access document processing tools for extracting text, generating summaries, and identifying skills via MCP.
-
docflow-mcp
Related Servers
Alternatives to docflow-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to extract structured data from PDFs with confidence scores and provenance, and to search, review, and correct documents via MCP tools, resources, and prompts.-
flexorch-mcpofficial
AlicenseAqualityAmaintenanceEnables Claude and other MCP-compatible agents to process documents, extract structured data, detect PII, and export LLM-ready datasets through natural language tool calls.8155 PyPI1MIT- AlicenseBqualityDmaintenanceEnables AI assistants to interact with Labradoc's document management, email ingestion, task extraction, and integration features through MCP tools.176 npmMIT
- FlicenseAqualityBmaintenanceEnables LLMs to ingest and analyze legal agreements, compute risk scores, and monitor non-compliant clauses through MCP tools like ingest, fetch_contracts, and run_analysis.4-
- FlicenseNot gradedqualityCmaintenanceThe Documentize MCP server exposes all document processing capabilities as tools for AI agents and LLM clients — convert, merge, extract, sign, and more, directly from Claude Desktop, VS Code Copilot, Cursor, or any MCP-compatible host.-
TDQS
B3/5.0
Scored across 41 tools
Disambiguation4/5
Each tool targets a distinct resource/action such as workspace, category, field, table, sample, review repo/rule/task, or file, so descriptions mostly prevent ambiguity. Some close pairs like retry_review_rule vs retry_review_task or update_category vs update_category_field require careful reading, but the boundaries are clear enough.
Naming Consistency4/5
All tools share the docflow_ snake_case prefix and generally follow a verb-first naming pattern, making the set predictable. Minor inconsistencies like delete_category_tables vs add_category_table, or the less explicit upload_and_extract, prevent a perfect score.
Tool Count2/5
41 tools is well above the 25+ threshold and feels too heavy for an agent to efficiently select from, even though the domain is broad. Many tools are narrow API endpoints for closely related subresources that could potentially be consolidated.
Completeness3/5
File and category coverage is fairly complete with create/read/update/delete operations, but review-rule management has a notable gap: there is no explicit way to add a new rule or rule group to an existing repository, only update/delete and whole-repo setup. There is also no list-review-tasks operation, which creates partial dead ends in review workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues