MCP Server for Wave
Related Servers
Alternatives to MCP Server for Wave
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceThis 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.3MIT
- FlicenseNot 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.4-
- AlicenseAqualityDmaintenanceEnables Wave invoicing operations including listing invoices, retrieving details, and generating branded PDFs directly from AI assistants.57 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.4 npm1ISC
- FlicenseBqualityDmaintenanceA complete MCP server for Wave Accounting, providing comprehensive access to invoicing, customers, products, transactions, bills, estimates, taxes, and financial reporting.54-
- 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
Most tools are clearly distinct list/get pairs per resource, but wave_list_account_types vs wave_list_account_subtypes are easy to confuse, and the auth-related tools (wave_get_user, wave_get_oauth_application, wave_auth_status) have overlapping purposes. The duplicate wave_get_vendor entry in the listing adds a small amount of ambiguity.
The wave_<verb>_<resource> convention is followed for nearly every tool, with list/get used consistently. Minor deviations like wave_auth_status (no verb) and wave_get_invoice_estimate_settings (compound resource name) prevent a perfect score.
30 tools is high for a read-only server, but it does cover many distinct Wave resources with list+get pairs. Several tools could reasonably be consolidated (e.g., currency/country/province lookups, account types/subtypes), making the set feel heavier than necessary.
The server is entirely read-only—no create, update, or delete tools exist—yet wave_auth_status says it reports whether write tools are enabled, and wave_list_account_subtypes references a wave_create_account tool that is not present. This leaves major workflows like creating invoices or customers impossible, which is a significant gap for a Wave connector.