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.11544 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.30597 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.8/5.0
Scored across 22 tools
Disambiguation4/5
Most tools target a distinct resource+action (get_workspace, list_messages, pay_invoice, sign_contract), and descriptions carefully separate the portal-session vs flow-credential families. However, there is real conceptual overlap between get_workspace (a 'vendor project') and get_project (the portal's Overview), and between list_workspace_files and list_attachments, which could cause occasional misselection.
Naming Consistency4/5
Nearly the entire set follows a snake_case verb_noun convention (list_projects, get_message, send_message, sign_contract, pay_invoice, mark_messages_seen). The only deviation is honeybook_healthcheck, which uses a server-prefixed style rather than a verb_noun form.
Tool Count4/5
22 tools is on the heavy side but justified by a genuinely broad client-portal domain spanning credentials, projects, workspaces, files, payments, messages, tasks, notes and meetings. No tool appears obviously redundant.
Completeness3/5
Read coverage is thorough across the portal, but write/action coverage is thin: clients cannot submit questionnaire answers (get_flow only reads them), upload or share files, or perform most mutating actions beyond messaging, signing and paying. These gaps could cause dead ends for common client workflows.
Maintenance
ActivityActive
ResponsivenessResponsive