F
licenseNot graded
qualityD
maintenanceA Model Context Protocol server that enables Claude (or any MCP client) to read and write Clio Manage data—contacts, matters, activities—directly from chat, with flat-fee billing support in one call.
-
honeybook-mcp
by chrischall
Related Servers
Alternatives to honeybook-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables seamless integration between Claude AI and development tools like VSCode, Augment, Vercel, Airtable, and Square.7MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server that connects Claude to OurFamilyWizard, giving you natural-language access to your co-parenting messages, calendar, expenses, and journal.11843 npm1MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server that connects Claude to OurFamilyWizard, giving you natural-language access to your co-parenting messages, calendar, expenses, and journal.28833 npm14MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server that gives Claude (or any MCP-compatible LLM) direct access to a self-hosted WordPress site over its REST API.73MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects Claude to your Google Sheets for personal finance tracking, analysis, and reporting — all through natural language.2-
TDQS
A3.9/5.0
Scored across 22 tools
Disambiguation4/5
Nearly every tool targets a distinct resource plus action, and the descriptions proactively disambiguate the tricky pairs (list_attachments vs list_workspace_files, use_magic_link vs use_flow_link, list_payments vs list_payment_methods). The one soft spot is the workspace vs project duality (get_workspace/list_projects/get_project), where the relationship could momentarily confuse an agent, but the descriptions clarify it.
Naming Consistency4/5
The set is overwhelmingly consistent snake_case verb_noun (list_notes, get_workspace_file, send_message, mark_messages_seen). Minor deviations are honeybook_healthcheck (noun_noun) and the use_*_link auth tools, but these remain readable and predictable.
Tool Count4/5
22 tools sits in the heavier band, but the domain is genuinely broad (auth sessions, flows, workspaces, files, payments, messages, meetings, tasks, notes) and each tool maps to a real capability. Nothing looks redundant or padded, so the count is justified though on the larger side.
Completeness4/5
Strong read coverage across workspaces, files, projects, messages, payments, meetings, notes and tasks, plus messaging/sign/pay write paths. Gaps are minor: pay_invoice and sign_contract are deep-link stubs rather than headless actions, there are no per-item getters for notes/attachments, tasks cannot be marked complete, and there is no cross-workspace search.
Maintenance
ActivityActive
ResponsivenessResponsive