freshbooks-mcp
Related Servers
Alternatives to freshbooks-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceAn MCP server for the FreshBooks API that lets Claude read and manage invoices, clients, expenses, projects, services, payments, and time entries.-
- FlicenseNot gradedqualityAmaintenanceAn MCP server that connects Claude to FreshBooks, enabling reading and management of invoices, clients, expenses, projects, and time entries via natural language.1-
- AlicenseBqualityDmaintenanceProduction-grade MCP server for FreshBooks. 25 tools for invoices, clients, expenses, payments, time tracking, projects, estimates, and financial reports. OAuth2 with automatic token refresh.253MIT
- FlicenseNot gradedqualityDmaintenanceProvides 29 tools for Claude to query and update FreshBooks directly, including invoices, clients, estimates, expenses, payments, timesheets, and reports.-
- FlicenseNot gradedqualityDmaintenanceAutomates FreshBooks invoicing and time tracking through Claude, allowing users to send invoices, list invoices, log billable hours, and get financial insights via natural language commands.2-
- AlicenseNot gradedqualityCmaintenanceMCP server for the FreeAgent accounting API, enabling LLMs to securely access and manage accounting data including contacts, invoices, bills, bank transactions, and more.5 npm1MIT
TDQS
Scored across 34 tools
Tools are organized by resource and action, and most are clearly distinct. The main ambiguity is the generic list_records/get_record pair, which can also target resources that have dedicated list/get tools, so an agent might occasionally pick the generic reader instead of the typed one.
All tools share the freshbooks_ prefix and use snake_case with a mostly verb_noun pattern (list_clients, get_invoice, create_project). Minor outliers like freshbooks_auth_url, freshbooks_healthcheck, and freshbooks_auth_exchange are noun-ish rather than verb-first, but the overall scheme remains predictable.
34 tools is on the heavy side for an MCP server, and the generic list_records/get_record pair duplicates much of the typed read surface. However, FreshBooks has several distinct resource domains (clients, invoices, estimates, expenses, projects, time, items, payments), so the count is not completely unjustified.
The surface has notable gaps: there is no create_estimate, no update or delete for clients/expenses/projects/time entries, no invoice send/delete action, and items are read-only. These missing operations will cause real agent failures when trying to execute common accounting workflows.