MCP Server for Wave
Related Servers
Alternatives to MCP Server for Wave
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceThis MCP server enables AI assistants like Claude to perform Wave Accounting bookkeeping tasks—such as drafting invoices, managing customers, recording payments, and looking up financial data—through natural language commands.7MIT
- AlicenseNot gradedqualityDmaintenanceComprehensive MCP server for Wave Accounting, providing 45+ tools across invoicing, customers, products, transactions, bills, estimates, taxes, and financial reporting, plus 17 pre-built UI workflows.5MIT
- AlicenseAqualityDmaintenanceEnables Wave invoicing operations including listing invoices, retrieving details, and generating branded PDFs directly from AI assistants.53 npmISC
- AlicenseNot gradedqualityDmaintenanceProvides 54 tools across 10 categories for Wave Accounting, enabling invoicing, customer management, products, transactions, bills, estimates, taxes, businesses, and financial reporting through Wave's GraphQL API.10 npm1ISC
- AlicenseBqualityDmaintenanceA complete MCP server for Wave Accounting, providing comprehensive access to invoicing, customers, products, transactions, bills, estimates, taxes, and financial reporting.54MIT
- FlicenseAqualityFmaintenanceMCP server for Wave accounting that provides tools for managing chart of accounts, invoices, customers, vendors, products, and reports via the Wave GraphQL API.6-
TDQS
Scored across 30 tools
Each tool targets a distinct resource+action, and the list/get pairs (customers, vendors, products, taxes, invoices, estimates, accounts) are clearly separated. Descriptions even preempt overlaps, e.g. wave_get_invoice_payment vs wave_get_invoice, and wave_get_province vs wave_get_country. No two tools appear interchangeable.
Every tool follows the same wave_verb_noun pattern (wave_list_*, wave_get_*, wave_set_*), all snake_case, with a uniform namespace prefix. There are no stylistic deviations or mixed conventions.
30 tools is heavy for a read-only surface, and several low-value pairs inflate it (account_types + account_subtypes, get_country + get_province, currencies list/get). Consistent list+get pairs per entity are defensible, but the set is near the top of the reasonable range and could be consolidated.
The surface is almost entirely reads: there is no create/update/delete for invoices, estimates, customers, products, or accounts, despite wave_auth_status advertising 'write tools' and wave_list_account_subtypes referencing a wave_create_account that does not exist. Agents following those descriptions hit dead ends.