Skip to main content
Glama
oliverames

MCP Server for Wave

by oliverames

Related Servers

Alternatives to MCP Server for Wave

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      This 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.
      3
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Comprehensive 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
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables Wave invoicing operations including listing invoices, retrieving details, and generating branded PDFs directly from AI assistants.
      5
      7 npm
      ISC
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides 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 npm
      1
      ISC
    • F
      license
      B
      quality
      D
      maintenance
      A complete MCP server for Wave Accounting, providing comprehensive access to invoicing, customers, products, transactions, bills, estimates, taxes, and financial reporting.
      54
      -
    • F
      license
      A
      quality
      F
      maintenance
      MCP 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

    A3.6/5.0

    Scored across 30 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow