F
licenseNot graded
qualityC
maintenanceEnables AI assistants to securely search and list internal company documents via MCP tools, so they can answer employee questions based on current internal documentation.
-
laserfiche-mcp
Related Servers
Alternatives to laserfiche-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with Labradoc's document management, email ingestion, task extraction, and integration features through MCP tools.176 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables document conversion and processing through an MCP server interface for AI assistants.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query documents in a Bedrock Knowledge Base through the MCP protocol, with tools for semantic search and agentic retrieval.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to read documents in Excel, DOCX, PDF, and TXT formats via MCP protocol.197 PyPI23MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to securely search and ingest corporate documents via MCP, offering hybrid retrieval, PII sanitization, role-based access control, and citation validation.MIT
TDQS
A3.9/5.0
Scored across 22 tools
Disambiguation3/5
Most tools target distinct resources, and the search family is carefully differentiated (raw, by name, content, natural). However, task_get_status, task_wait, and task_update overlap significantly—task_update explicitly subsumes the other two—and document_get_text overlaps with document_get_edoc(mode="text"), making selection ambiguous.
Naming Consistency4/5
All tools share the laserfiche_ prefix and mostly follow a <resource>_<action>_<qualifier> pattern, so the set is predictable. Minor inconsistency: 'definition_list' appears as a suffix in some tools while others use 'get' or 'field_list,' and search variants use different qualifier positions, but nothing is chaotic.
Tool Count3/5
22 tools is at the high end of reasonable and each definition-lister has a distinct resource, so the count is not absurd. It feels heavier than necessary because three task tools and two document-text tools could be consolidated, and several definition listers are only useful if absent write tools existed.
Completeness2/5
The set covers search, retrieval, metadata, and definitions very well, but it is a read-only surface: there are no create/update/delete/import tools. Descriptions repeatedly reference absent write/async tools like delete_entry, copy_entry, assign_template, set_tags, and set_links, so workflows like cleaning up duplicates dead-end.
Maintenance
ActivityMaintained
ResponsivenessNo issues