Wave MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOGO_PATH | No | Path to logo PNG (default: ./assets/logo.png) | |
| WAVE_API_KEY | Yes | Your Wave full-access token | |
| BUSINESS_NAME | No | Business name on invoices | |
| BUSINESS_PHONE | No | Phone number | |
| WAVE_BUSINESS_ID | Yes | Your Wave business ID | |
| BUSINESS_ADDRESS1 | No | Address line 1 | |
| BUSINESS_ADDRESS2 | No | Address line 2 | |
| INVOICE_OUTPUT_DIR | No | Output directory for PDFs (default: ./invoices) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_invoicesA | List invoices from Wave with pagination |
| get_invoiceA | Get full details of a specific invoice |
| list_customersA | List all customers from Wave |
| export_invoice_jsonC | Export Wave invoice to JSON format |
| generate_invoice_pdfA | Fetch invoice from Wave and generate a branded PDF. Returns the path to the generated PDF. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: list_invoices vs get_invoice separates collection from detail, and export_invoice_json vs generate_invoice_pdf are explicitly different output formats. list_customers is entirely separate from the invoice workflow.
All tools follow a consistent lower_snake_case verb_noun pattern, with singular/plural usage matching intent (list_invoices vs get_invoice). The export/generate tools extend the pattern with an output format, which is still predictable.
Five tools is well-scoped for a focused Wave integration covering invoice retrieval, customer listing, and invoice export. Each tool earns its place without redundancy or bloat.
The invoice retrieval and export workflow is covered, but the surface has notable gaps such as no create/update/delete for invoices and no customer detail lookup. Agents can perform read-only and export tasks, but cannot complete full invoice management workflows.