F
licenseNot graded
qualityC
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.25699 npm10MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server that connects Claude to OurFamilyWizard, giving you natural-language access to your co-parenting messages, calendar, expenses, and journal.11831 npm1MIT
- 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.8/5.0
Scored across 22 tools
Disambiguation4/5
Most tools clearly target a distinct resource and action, with list_/get_/use_ prefixes separating concerns. A few boundaries require careful reading—get_project vs get_workspace overlap, and list_workspace_files vs list_attachments split by file type—but the descriptions provide enough differentiation.
Naming Consistency4/5
The naming is largely consistent: list_* for collections, get_* for single resources, and use_* for credential capture. The main deviation is honeybook_healthcheck, which breaks the verb_noun pattern, and mark_messages_seen is slightly awkward but still readable.
Tool Count3/5
At 22 tools, the set is on the heavy side and fits the '16-25 feels heavy' band. The broad domain justifies many of them, but the numerous narrow list_* tools create a large surface that an agent must navigate.
Completeness4/5
The surface covers core client-portal workflows well: authentication, projects, files, messages, tasks, meetings, notes, attachments, payments, contracts, and invoices. Minor gaps exist—no attachment detail retrieval, no task/meeting action tools, and no payment method management—but agents can work around these.
Maintenance
ActivityNo data
ResponsivenessResponsive