A
licenseNot graded
qualityD
maintenanceEnables Claude to interact with collaborative Docs instances, providing document management, content editing, access control, and AI-powered transformations via MCP.
1
MIT
@lazco-studio/huly-mcp
Related Servers
Alternatives to @lazco-studio/huly-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceConnects MCP clients such as Claude Code to a self-hosted La Suite Docs instance, letting them full-text search, browse by recency or favorites, read documents as markdown, and create or edit content (including single-section edits). Favorited documents are also exposed as MCP resources so they can be @-mentioned straight into context.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients like Claude Desktop and Cursor to interact with Google Docs, Sheets, and Drive, providing tools for reading, writing, formatting documents, managing spreadsheets, and searching Drive files.MIT
- FlicenseCqualityDmaintenanceEnables Claude to interact with Hudu IT documentation, including searching, reading, creating, and updating articles, assets, passwords, companies, and more.100-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to read, search, create, and edit Quip documents through the MCP protocol.5ISC
- FlicenseAqualityBmaintenanceEnables reading, creating, updating, and appending Feishu documents, as well as querying and updating Bitable fields and records via the MCP protocol.12-
TDQS
A3.7/5.0
Scored across 12 tools
Disambiguation5/5
Every tool pairs a clear verb with a distinct resource: teamspaces, documents, projects, issues, and the current user. list_documents and search_documents are differentiated by browsing vs. keyword search, and get_document vs. get_issue target completely different object types.
Naming Consistency5/5
All tools use the huly_ prefix and follow a snake_case verb_noun pattern (list_, get_, create_, update_, delete_, search_, comment_). huly_whoami is the only slight outlier but is a conventional identity-check idiom and does not disrupt the overall consistency.
Tool Count5/5
12 tools is well within the ideal scope for an integration server. The toolset covers two coherent resource families—documents and issues—with no redundant utilities or unnecessary bloat.
Completeness2/5
The document side has full lifecycle coverage (list, get, search, create, update, delete), but the issue side only supports list, get, and comment. Missing issue creation, update, deletion, and state transitions are significant gaps that prevent common issue-management workflows.
Maintenance
ActivityMaintained
ResponsivenessNo issues