Skip to content

Accounting

Wave MCP connector

The Wave connector lets Claude, ChatGPT, Cursor, or any MCP client create and update customers, estimates, and chart of accounts entries in Wave, with every action running under the signed-in person's own Wave access and recorded in an audit log.

  • How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Wave to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Wave once

  1. Open Connections, choose Add connection, and pick Wave.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Approve it in Wave. Wave's own window opens. Whoever approves it decides what this connection can reach.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

wave
Wave
Buildium
DualEntry
FloQast
FreshBooks
Invoiced
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Wave to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Wave to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Wave to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Wave to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Wave through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Sales

    Turn a yes into an invoice

    When a customer accepts a quote, have the Wave estimate marked accepted and converted to an invoice in one ask, without opening Wave.

  • Sales

    Clone last quarter's estimate for a repeat order

    Duplicate an existing Wave estimate, change the quantities or dates, and generate the PDF ready to send.

  • Finance

    Keep the chart of accounts tidy

    Add a new account under the right type and subtype, rename one that has drifted, or remove one nobody posts to, all in Wave.

  • Finance

    Send the deposit receipt right away

    Once a deposit arrives against an estimate, have Wave send the deposit payment receipt to the customer so nobody has to chase it.

  • Office

    Set up a new customer from an email

    Paste in a signature block and have the customer created in Wave, then correct the billing address or contact when it changes.

  • Leadership

    Confirm which business and currency you are billing in

    Ask which Wave businesses you can see and which currencies and countries they use before an estimate goes out in the wrong one.

Try asking

  • “List unpaid invoices for our top ten Wave customers.”
  • “Which Wave accounts changed balance this month?”
  • “Draft a new customer in Wave for Northside Dental.”

See all 51 Wave tools below

AI tools

Wave tools for your AI agents

51 tools are ready to call through Elaichi's MCP endpoint the moment you connect Wave, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Wave gets you

6 screens from the product, each doing one job for your Wave account.

The agent

Ask about invoices, get real answers.

Plain questions run against live Wave customers, accounts and invoices.

  • invoices
  • customers
  • accounts
  • businesses

Ask Elaichi to work across your apps.

List unpaid invoices for our top ten Wave customers.

Which Wave accounts changed balance this month?

Draft a new customer in Wave for Northside Dental.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Wave.

One org MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

51 Wave tools, zero custom code.

Businesses, accounts, customers, invoices and currencies, each with listed resources and methods.

  • Wave users me
  • Create a Wave account
  • Delete a Wave account by ID
  • Update a Wave account by ID
ElaichiTools
Tool Action Description
Wave users me Action Get the currently authenticated Wave user. Returns: id, defaultEmail, firstName, lastName, createdAt, modifiedAt.
Create a Wave account Create Create a Wave account via the accountCreate mutation. Required input: businessId, name, subtype. Returns the created account with id, name, currency, type, and subtype. inputErrors[] surfaces field-level validation failures.
Delete a Wave account by ID Delete Delete (archive) a Wave account via the accountArchive mutation. Required: input.id (account ID). Returns didSucceed and any inputErrors for validation failures.
Update a Wave account by ID Update Update (patch) a Wave account via the accountPatch mutation. Required input fields: id, sequence. Optional: name, description, displayId. Returns the patched account and any inputErrors for validation failures.
Create a Wave customer Create Create a Wave customer via the customerCreate mutation. Required: input (object with businessId, name). Returns the created customer. inputErrors[] surfaces field-level validation failures.

Toolboxes

Every team gets its own Wave toolbox.

Bookkeeping, sales and payroll each work from a toolbox scoped to them.

  • Bookkeeping
  • Accounts receivable
  • Sales
  • Finance leadership
ElaichiToolboxes
Name Source template Tools Created

Bookkeeping toolbox

Wave · accounts and account types

Wave starter 18 Mar 4, 2026

Accounts receivable toolbox

Wave · invoices and customers

9 Mar 2, 2026

Sales toolbox

Wave · customers and quotes

24 Feb 27, 2026

Finance leadership toolbox

Wave · businesses and currencies

Wave starter 6 Feb 19, 2026

Payroll toolbox

Wave · accounts and vendors

31 Jan 30, 2026

Tax and compliance toolbox

Wave · countries and sales taxes

12 Jan 22, 2026

Shared connections

Share a Wave business, never the login.

See who connected each account and how many teams and members use it.

  • Bookkeeping
  • Accounts receivable
  • Sales EMEA
  • Payroll
ElaichiConnections
Connection Scope Status Access
WA

Wave (Bookkeeping)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
WA

Wave (Accounts receivable)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
WA

Wave (Sales EMEA)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
WA

Wave (Payroll)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
WA

Wave (Finance leadership)

Connected by Clara Nowak

Personal • Active Not shared
WA

Wave (Tax and compliance)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Wave call has a name on it.

When, who, what happened, type and resource for each invoice and account change.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Wave Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Wave Invoices Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Wave Invoices List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires, Wave work gets done.

Invoices are fetched, grouped, drafted into a digest, approved, then posted back.

Wave digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch invoices

    Wave

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Wave

    Queued

Collections and dashboards

Wave numbers arrive before anyone asks.

Four metrics, 14 days of invoices created, split by team, refreshed on schedule.

Wave health

Refreshed 4 minutes ago · every 15 minutes · from the invoices collection

Live

Invoices

1,284 ↓ 12%

Customers

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Invoices created

Last 14 days

By team

Share of activity

Bookkeeping 34%

Accounts receivable 27%

Sales EMEA 21%

Payroll 18%

FAQ

Frequently asked questions

How do I connect Wave to Claude?

Connecting Wave to Claude takes two steps. First, connect Wave in Elaichi: you are sent to Wave's own sign-in window, you log in and approve, and there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and Wave is then available in your conversation.

Does Wave work with ChatGPT and Cursor as well as Claude?

Yes. Once Wave is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Wave once and every client you use picks it up, with the same permissions and the same audit log.

What can an AI agent actually do with my Wave data?

With Wave connected, an agent can create, update, and remove customers, build and edit estimates, mark an estimate accepted, convert it to an invoice, clone it, generate its PDF, and send a deposit payment receipt. It can also add or change accounts in your Wave chart of accounts and look up which businesses, currencies, and countries your account uses. Wave has many actions available, so short, specific asks such as "convert estimate 1042 to an invoice" work better than long paragraphs.

Does connecting Wave give the AI access to every business in my account?

No. An agent working through Wave sees exactly the businesses, customers, and estimates that the person who signed in can see, and nothing more, because every call runs inside that person's own Wave access. Elaichi can narrow that further, for example by taking away the ability to delete customers, but it can never grant anything Wave itself would not allow that person.

Can my team share one Wave connection?

Yes. One person connects Wave in Elaichi and shares it with a team, and nobody else ever handles a Wave credential or sees a token. Each teammate still signs in to Elaichi as themselves, so every estimate created or customer changed in Wave is logged against the individual who did it, not against the person who set up the connection.

Can I stop an agent from deleting or changing things in Wave?

Yes. Restrictions in Elaichi work per action, so you can allow an agent to create and update Wave customers and estimates while blocking deletion of customers, estimates, or accounts entirely. A blocked action is never shown to Claude, ChatGPT, or any other client at all, so no prompt, however worded, can reach it.

What happens to a Wave connection when someone leaves?

When you offboard someone in Elaichi, their access to Wave through every client ends immediately, whether they were using Claude, ChatGPT, Cursor, or the Elaichi Agent. If they had shared a Wave connection with a team, it keeps working for everyone else on that team. If you ever want Wave gone completely, disconnecting it once in Elaichi removes it from every client at the same time.

Put Wave in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.