freshbooks-mcp
Related Servers
Alternatives to freshbooks-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server for the FreshBooks API that lets Claude read and manage invoices, clients, expenses, projects, services, payments, and time entries.-
- FlicenseNot gradedqualityCmaintenanceAn 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.-
- AlicenseNot gradedqualityCmaintenanceEnables Claude and other MCP clients to log, update, and delete FreshBooks time entries, run and stop timers, and pull summaries of billable and unbilled hours by day, week, client, project, or service, with OAuth-based sign-in and per-user token storage.MIT
- 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-
TDQS
Scored across 34 tools
Each dedicated tool targets a distinct resource+action, and the freshbooks_ prefix plus resource noun makes per-resource selection straightforward. The main fuzziness comes from the generic get_record/list_records overlapping with the dedicated getters/lists, and from decline_estimate being a deliberately failing tool, but the descriptions call both out explicitly.
Every tool follows the same freshbooks_verb_noun pattern (list_invoices, get_invoice, create_invoice, update_invoice, record_payment), with singular nouns for single-record operations and plural for collections. Even the odd-man-out (decline_estimate) fits the verb_noun convention.
34 tools is heavy for what is essentially one accounting domain, and some of the load is redundancy: generic get_record/list_records duplicate the per-resource readers, and decline_estimate exists solely to return an error. The breadth (invoices, estimates, clients, payments, items, expenses, projects, time, services, auth) does justify a large surface, so it is borderline rather than excessive.
Read coverage is strong and the invoice/estimate lifecycles are well served (create, update, send, accept), but there is no delete anywhere and no update for clients, expenses, projects, time entries, or line-item edits beyond update_estimate. Agents can read most things via get_record/list_records, but write workflows beyond invoices and estimates will dead-end.