MYOB MCP Server

Invoices, bills and payments in MYOB.

Размещённый MCP-сервер

npx add-mcp 'https://cotlet.dev/mcp/v1/myob'

Устанавливается в Claude Code, Codex, Cursor и другие

Документация

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

MYOB API and MCP server: Let your AI agent do the invoicing and bills in MYOB.

MYOB's official connector for Claude and ChatGPT only answers questions, and its Business API is open to developers MYOB admits (checked 27 Oct 2026). Cotlet runs 12 MYOB tools hosted, over MCP for agents and REST for scripts, on Lite, Pro or AccountRight in the browser.

Invoices, bills and payments in MYOB. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

MCP setup REST API guide

What can you automate in MYOB?

  • Create invoices from a billing list
  • Email invoices to customers
  • Record payments against open invoices
  • Enter supplier bills without doubles
  • List overdue invoices every Monday
  • Add new customers from a form

Does MYOB have an MCP server or an API?

  • The MYOB connector, announced 17 Aug 2026, has six read-only tools such as profit and loss and customer balances. It is a beta for invited MYOB Business Pro customers in Australia.
  • The Business API creates invoices, bills, payments and customers, but you apply for a developer account first, MYOB support tells business owners not to apply for keys themselves, and an Admin of each company file grants OAuth consent.
  • No API action emails an invoice or a statement. Zapier has no MYOB app; n8n has community nodes that need your own OAuth app.
What you needMYOB connectorBusiness APICotlet
Read balances and overdue invoicesYesYesYes
Create invoices, bills, customersRead-onlyYesYes, after your OK
Record customer and supplier paymentsNoYesYes, after your OK
Email an invoice or a statementNoA flag, no sendYes, after your OK
What you need firstInvite, Pro, AustraliaDeveloper approval, OAuth appYour MYOB login
Made by MYOBYesYesNo, uses your browser login

Checked 27 Oct 2026. Sources: MYOB press release: SME financial intelligence in ChatGPT and Claude, MYOB Developer Centre: Getting started with the Business API, MYOB API support: a developer has asked me for an API key, MYOB Developer Centre: Sale/Invoice, Zapier: MYOB

How does Cotlet connect to MYOB?

  1. Sign in to MYOB. Use your own account in its Cotlet Cloud Browser.
  2. Choose MCP or REST. Connect your agent or create a Cotlet API key.
  3. Run your workflow. Ask your agent or send an HTTP request.

We never keep your MYOB password, and no invoice, email, payment or bill is saved or sent before you approve it.

Connect MYOB to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

  1. Sign in to MYOB in a Cloud Browser. Create a Cotlet account, open MYOB in its Cloud Browser, sign in to MYOB Business with your own my.MYOB login and press Enable for agents.
  2. Add the Cotlet address. Paste https://cotlet.dev/mcp/v1 into the MCP server or custom connector field of your agent.
  3. Approve the connection. Chat apps send you to a Cotlet sign-in page. Code editors, n8n and scripts send an API key from the console.

MYOB asks for a two-factor code in every new browser, so you type it once in the Cloud Browser and tick Trust this device for 30 days. The tools work on the business you have open; a bookkeeper with several clients opens the right file before a run. https://cotlet.dev/mcp/v1 serves MYOB next to your other Cotlet apps; refresh the connector after enabling MYOB so its tools load.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: myob_read

Make, Zapier:

Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: myob_write

How to use the MYOB REST API

Create your Cotlet API key

Create a Cotlet API key with access to MYOB and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect MYOB in Cotlet and enable it for agents. Account access: Your own MYOB Business login (my.MYOB), with access to the company file and to the Sales and Purchases menus.

Make your first MYOB API request

REST:

curl "https://cotlet.dev/api/v1/myob/customers?limit=5" \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read customers and apply the operation limits

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "myob",
  "tool": "list_customers",
  "result": {
    "customers": [
      {
        "customer_id": "CUS000012",
        "name": "Harbour Cafe Pty Ltd",
        "email": "accounts@harbourcafe.example",
        "terms": "In a given number of days: 14",
        "active": true
      }
    ],
    "next_cursor": null
  }
}

Returns customer cards in alphabetical order. Search matches the name, the card ID or the email.

Active customers are returned unless include_inactive is true. Use customer_id from each item in create_invoice, record_invoice_payment and send_customer_statement.

Pages hold up to 100 customers; pass next_cursor back as cursor for the next page.

limit: 1 to 100. Default: 50.

cursor: Next page cursor from the previous call.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

MYOB workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestSales invoices with customer, dates, total and balance due, filtered by status. Use list_invoices in your configured operations sheet.
MakeHTTP > Make a requestOne sales invoice with lines, tax, payments applied and activity history. Use get_invoice in your configured operations sheet.
Python or Node.jsREST APISupplier bills with supplier, dates, total and balance due, filtered by status. Use list_bills in your configured operations sheet.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads MYOB; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

MYOB API endpoints and MCP tools

Customers and invoices

A new invoice stays open and unsent until send_invoice emails it from the Share menu. A customer card without an email address cannot be sent to, so the agent reads the card first.

  • List customers (list_customers, read): Customer cards with card ID, name, email and payment terms, filtered by name or email.
  • Create customer (create_customer, write): Add a customer card with name, email and payment terms.
  • List invoices (list_invoices, read): Sales invoices with customer, dates, total and balance due, filtered by status.
  • Get invoice (get_invoice, read): One sales invoice with lines, tax, payments applied and activity history.
  • Create invoice (create_invoice, write, asks first): Create a sales invoice for a customer with one or more lines.
  • Send invoice (send_invoice, write, asks first): Email an invoice to the customer with the PDF attached.

Payments

Money goes in or out of the bank account you name from list_bank_accounts. A payment matched or reconciled in Banking cannot be changed, and no tool picks Electronic payment, so MYOB never pays a supplier.

  • List bank accounts (list_bank_accounts, read): Bank accounts and credit cards you can record payments in or out of.
  • Record invoice payment (record_invoice_payment, write, asks first): Record money received from a customer against one or more open invoices.
  • Record bill payment (record_bill_payment, write, asks first): Record a payment to a supplier against one or more open bills.

Supplier bills

Give the supplier's own invoice number on every bill, so list_bills can spot one that was already entered.

  • List bills (list_bills, read): Supplier bills with supplier, dates, total and balance due, filtered by status.
  • Create bill (create_bill, write, asks first): Enter a supplier invoice as a bill with its lines and tax.

Statements

An invoice statement lists what is unpaid on a date; an activity statement lists invoices and payments between two dates.

  • Send customer statement (send_customer_statement, write, asks first): Email a customer statement as a PDF to one or more customers.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/myob-api-mcp-server#tools

Who can see my MYOB session, and how do I revoke it?

  • What we store. The signed-in MYOB browser profile, AES-256-GCM encrypted, in Finland. Never your password.
  • What your agent gets. 12 MYOB tools. Not the session cookie or the login.
  • What the session sees. What your MYOB user role sees in the open business.
  • What no tool touches. Electronic payments, bank feeds, payroll, BAS, users and deletes.
  • If MYOB asks for a code. You type the two-factor code yourself. We never do.
  • How to cut access. Disable for agents, reset the browser, or remove the user in MYOB.

Your books hold customer and supplier bank details, so give the agent a MYOB user with only Sales, Purchases and Banking access and it never sees payroll. The Cotlet site has A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results); we have no SOC 2 report or third-party pentest yet.

Is it against MYOB's terms? Account safety

You should never: tell anyone your username and password; or let anyone else, whether acting as your agent or not, access AccountRight using your username and password.

MYOB AccountRight terms, section 1.4 (last updated March 2024; the MYOB Essentials terms say the same)

MYOB's terms and EULA name no bots, scripts or scraping. The login rule is the risk: Cotlet never sees your password, but an agent working in your session could be read as someone acting for you. The EULA also lets MYOB suspend a login "used by more than one individual". Lite, Pro and AccountRight have unlimited user profiles, so the safer setup is a separate MYOB user for the agent, invited by the owner with only Sales, Purchases and Banking access. We found no public case of a MYOB account closed over automation (checked 27 Oct 2026).

How we keep your account looking like you:

  • A MYOB login you type in yourself, ideally its own user
  • One Cloud Browser with a steady IP and cookies, trusted once for 2FA
  • Invoices, emails, payments and bills wait for your OK
  • No tool deletes a record or moves money from the bank
  • If MYOB objects, we pause the MYOB tools for everyone within 24 h

Five wrong two-factor codes lock a MYOB login for 20 minutes. The code is always yours to type; nothing guesses it for you.

What happens when MYOB changes?

  • 12 h between tests of the MYOB invoice, bill and customer reads
  • 24 h between tests of invoice emails, payments and bills
  • $0 for a call to a MYOB tool paused for repair

MYOB moves often: the old CompanyFile API scope stopped on 1 Sep 2026, the AI Assistant became Ask Iris on 19 Oct 2026, and the MYOB Invoice and Capture apps retire in New Zealand on 23 Nov 2026. The tools follow the MYOB Business browser screens, so an API scope change does not touch them; when a screen moves, we repair the tool under the same name. status.cotlet.dev checks the site, console and API every 3 minutes.

Approvals, undo and mistakes

  1. Matches customers. list_customers per line; unknown names go on a "needs you" list.
  2. Creates the invoice. create_invoice waits for your OK, then the total is checked against your list.
  3. Holds the email. send_invoice waits in your Cotlet console, with the address from the customer card.
  4. Reports the run. Invoice numbers, totals, and customers held for a missing email.
ActionUndo
Create a customerMark the card inactive or delete it while unused
Create an invoice or a billDelete it in MYOB while no payment is applied
Email an invoice or a statementNo, the customer has it; send a corrected one
Record a customer paymentDelete it, unless it is matched or reconciled in Banking
Record a bill paymentDelete it the same way; no money left your bank

6 of the 7 write tools ask first: every invoice, email, payment, bill and statement. create_customer runs at once, because a new card reaches nobody. Reads run at once too. For a scheduled run you can switch the wait off per tool.

An amount above the open invoices makes MYOB create a customer credit, so the agent reads the balance with get_invoice first and leaves an overpayment to you.

MCP call:

{
  "name": "create_invoice",
  "arguments": {
    "customer_id": "CUS000012",
    "date": "2026-10-14",
    "layout": "service",
    "lines": [
      {
        "description": "Bookkeeping, October",
        "quantity": 1,
        "unit_price": 1000,
        "tax_code": "GST"
      }
    ]
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/myob/customers/CUS000012/invoices \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date":"2026-10-14","layout":"service","lines":[{"description":"Bookkeeping, October","quantity":1,"unit_price":1000,"tax_code":"GST"}]}'

Response:

{
  "invoice_number": "00000142",
  "customer_id": "CUS000012",
  "customer": "Harbour Cafe Pty Ltd",
  "status": "open",
  "date": "2026-10-14",
  "due_date": "2026-10-28",
  "subtotal": 1000,
  "tax": 100,
  "total": 1100,
  "balance_due": 1100
}

A billing script or a nightly bank export job calls the same tools over REST at /api/v1/myob, with the same key and price. A call MYOB refuses, such as a payment into an account that does not exist, costs nothing. Each tool row above shows its REST path.

How much does the MYOB MCP server cost?

About $27 a month for a small business with about 40 invoices and 25 bills a month, 4,710 credits. MYOB still bills your plan, from AUD 315 a year for Lite.

JobCallsCredits
Create an invoice and email it3 × 401,200
Match and record a customer payment3 × 351,050
Enter a supplier bill, duplicate check first2 × 25500
Weekly bill payment run6 × 4240
Monday overdue report2 × 480
Statements to late payers, monthly2 × 120
New customers from a form2 × 6120
Cloud Browser, 30 days1,500
Total4,710
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • No developer account, OAuth app or Pro upgrade

MYOB publishes no invoice count per business, and most of its customers have fewer than 10 employees (6sense), so 40 invoices and 25 bills is our example. MYOB prices after the offer: Lite AUD 315 a year, Pro AUD 70 a month, AccountRight Plus AUD 165 a month. Solo is a phone app only and has no browser to sign in to. Dollars at the $29 pack rate.

MYOB MCP server on GitHub, hosted or paid: which to use

OptionWhat it doesWhere it stops
fixxdigital/myob-mcp-serverPython MCP server on the Business API: invoices, payments, bills. 0 stars, last push 7 Oct 2026.Needs your own approved developer key and secret; no license.
jaeko44/myob-codex-mcpPython MCP with reads by default and writes behind an approval token. MIT, 0 stars, last push 22 Oct 2026.Its README says live tests still wait for real MYOB developer credentials.
primrose-mcp/primrose-mcp-myobMCP over the AccountRight API: contacts, sales, purchases, payroll. 0 stars, last push 30 Jan 2026.You pass the access token, API key and company file ID yourself.
CData MCP for MYOB AccountRightFree local server, read-only, 4 stars. Read and write is in CData's paid products.Needs the paid CData JDBC driver; no emails.
Apideck MCP serverUnified accounting API with list, create, update and delete for MYOB invoices.A paid Apideck plan on top of a MYOB API connection.

If MYOB has approved you as a developer and you want to build, the Business API is the official route for invoices, bills and payments. If you only need answers from your books and you are an invited Pro customer in Australia, the MYOB connector is free. To have your agent create, email and record in MYOB without a developer account, Cotlet runs it hosted.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Take Group sp. z o.o. builds and runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), trading since 2019, and its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the MYOB tools go to contact@cotlet.dev.

MYOB API and MCP: questions

How do I get access?

Sign up free at https://cotlet.dev, open MYOB under Integrations in the console and sign in to MYOB Business in its Cloud Browser. The trial starts when you sign up and asks for no card.

How do I connect MYOB to ChatGPT or Claude?

Sign up at cotlet.dev, log in to MYOB once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your MYOB account through Cotlet, in their phone apps too.

What can ChatGPT do in MYOB?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in MYOB: create and email invoices from a list; record customer payments on invoices; enter supplier bills and pay them. You ask in plain words, and anything that reaches other people waits for your OK first.

Do I need a MYOB developer key or API access?

No. Cotlet signs in to your own MYOB account in a browser and does not use the Business API, which needs an access request, an app registered in my.MYOB and OAuth consent per company file. The tools run with the permissions your MYOB login already has.

Which MYOB products do the tools cover?

The tools follow the MYOB Business browser app: Sales > Invoices, Sales > Record invoice payment, Purchases > Bills and Purchases > Record supplier payment. A local AccountRight desktop file has no browser sign-in, so it is out of scope.

Does it work in New Zealand?

Yes. MYOB Business runs in the browser in Australia and New Zealand, and the tools use the tax codes of your own company file. The official MYOB connector is for Australia only.

Does it work with MYOB Solo?

No. Solo is a phone app only, with no browser sign-in. The tools need MYOB Business Lite, Pro or AccountRight in a browser.

Can I keep the MYOB connector and use Cotlet too?

Yes. Keep the official connector for questions about your numbers and add Cotlet to the same agent for the invoices, emails, payments and bills it cannot write.

Is the MCP server different from the REST API?

Only in how you call it. Both serve the same 12 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and scheduled jobs use REST.

Is Cotlet affiliated with MYOB?

No. Cotlet is independent and not affiliated with MYOB Australia Pty Ltd or MYOB NZ Limited.

Can I use the MYOB API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.


Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.