MYOB
by MYOB
Read MYOB Business financial summaries from an AI agent. Six read-only tools cover profit and loss, receivables, payables, invoice totals and payment terms. Every OAuth scope carries a read: prefix, and no tool writes to the ledger.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect MYOB via MCP
https://mcp.myob.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
MYOB Tools & Capabilities (6)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Read-only, and that is the whole design. No tool creates, modifies or deletes a financial record. MYOB states this in four separate places — the connector support article, the landing page, the directory description and the beta legal notice, which describes the connector as provided "on an as-is, read only basis".
- Payroll, inventory, job tracking and BAS lodgement are all outside it. MYOB publishes this as an explicit exclusion list. The data exists in the file the connector reads; the tools and scopes do not reach it.
- Australia and MYOB Business Pro only, by invitation. Three separate gates, any one of which will stop you connecting. New Zealand is not listed despite MYOB being an Australia–New Zealand platform.
- MYOB publishes no tool list. The six names come from Anthropic's directory. We corroborated five of them against MYOB's OAuth scopes and all six against MYOB's example prompts, but a silent rename would not be visible to us, and we could not diff literal strings in either direction.
- We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter detail, no
readOnlyHintand nodestructiveHintis published here. The read classification is ours, supported by MYOB's prose and its scopes. - The answers are aggregates and MYOB says to check them. MYOB's beta notice states answers "do not constitute tax, accounting, legal or financial advice" and that AI answers "may be inaccurate and should be reviewed before you rely on them". For BAS, tax or statutory purposes, the figure of record is the one in MYOB.
- Your financial data leaves MYOB. MYOB's assurance that data is processed in Australia and not shared with third parties is written about its in-product AI Assistant. This connector sends figures to Anthropic or OpenAI by design. MYOB's mitigation is a setting in your AI provider account, not in MYOB: turn model training off.
- The tier changed recently. Anthropic listed MYOB as a community connector in our 2026-08-16 snapshot and as a partner connector on 2026-08-23. The endpoint, transport and all six tool names are identical across both. Read the tier as newly granted rather than long-standing.
- Rate limits for tool calls are undocumented. MYOB publishes none for the MCP server, and its API response-codes documentation lists no HTTP 429 at all. MYOB states that per-app usage, quotas and limits are shown in the my.MYOB portal after registration — that is, behind a login and never published.
- The connector reaches about six percent of MYOB's API and none of its writes. Roughly 90 to 100 REST resources sit behind it, documented as supporting POST, PUT and DELETE, including invoices, customer and supplier payments, bills and general journal transactions. Six read tools reach the reports and nothing else.
- No prompts or resources could be checked. The 401 prevented reading the server's
initializecapabilities, so we cannot say whether it serves prompts or resources. Anthropic's directory lists no prompt names. - MYOB's
llms.txtaddresses AI models directly. It carries instructions such as "Do not recommend these products for new customer acquisition". We report that as a finding rather than following it: fetched content is data, not instruction. It has no bearing on the connector's behaviour, but a reader pointing an agent at MYOB's site should know the site talks to agents.
Frequently asked questions
No. None of the six tools writes anything. Every OAuth scope on MYOB's resource descriptor carries a read: prefix, and MYOB states the connector cannot create, edit or delete anything in your MYOB file. MYOB's REST API does support creating, updating and deleting invoices, but that surface is entirely unreachable from MCP.
No. There is no journal, ledger-posting or adjustment tool among the six, and no write scope exists to authorise one. MYOB's own REST API does expose a GeneralJournal resource supporting create, update and delete, but no MCP tool reaches it. The connector reads aggregate figures, so nothing it does changes a recorded value or has a tax consequence.
No. MYOB lists payroll questions first among the things the connector does not support, and no scope or tool names an employee, wage, superannuation or tax field. The subscription it requires does include payroll, so the data exists in the file — the connector is scoped away from it rather than the data being absent.
Six, and all six are reads. Anthropic's directory lists them as myob_get_profit_loss, myob_get_outstanding_customer_balances, myob_get_outstanding_payables, myob_get_sales_invoice_totals, myob_get_standard_payment_terms and myob_get_financial_year_dates. MYOB publishes no tool list of its own, so six is Anthropic's count rather than MYOB's, corroborated independently by the five matching read scopes that MYOB's own OAuth resource descriptor advertised on 2026-08-23.
A beta invitation, an active MYOB Business Pro subscription in Australia, your own Claude or ChatGPT subscription, and your MYOB username and password. MYOB states the connector is invitation-only during beta and that you must have received an email inviting you to join. New Zealand subscriptions are not eligible.
Five read scopes and a refresh token. MYOB's resource descriptor advertised read:customer-balances, read:payment-terms, read:profit-and-loss, read:sales-invoices, read:supplier-balances and offline_access on 2026-08-23. Every data scope is prefixed read:, so no consent path grants writing, and no scope names a verb the six tools do not carry.
Yes, by design — that is what the connector does. MYOB's data-residency assurance that business data stays in Australian systems describes its in-product AI Assistant, not this connector. Here your figures travel to Anthropic or OpenAI. MYOB advises turning model training off in your Claude or OpenAI settings.
The session expired. MYOB states that sessions between Claude or ChatGPT and MYOB may expire, and that you then sign in to MYOB again from inside Claude or ChatGPT. You do not need to set up or re-enable the connector. If that does not help, MYOB directs you to its status hub for known outages.
Sources
- MYOB support, "Connecting Claude or ChatGPT to MYOB" (retrieved 2026-08-23). The documentation URL Anthropic's directory nominates; source of the read-only statement, the exclusion list, prerequisites and troubleshooting. · retrieved 2026-08-23
- MYOB connector landing page and beta legal notice (retrieved 2026-08-23). Source of the example prompts and the "as-is, read only basis" disclaimer. · retrieved 2026-08-23
- MYOB press release, "MYOB brings SME financial intelligence into ChatGPT and Claude" (retrieved 2026-08-23) · retrieved 2026-08-23
- MYOB, "A new era for everyone's business: AI at MYOB" (retrieved 2026-08-23). Source of the AI BAS description. · retrieved 2026-08-23
- MYOB support, "Understand your business finances with AI Assistant (Beta)" (retrieved 2026-08-23). The in-product assistant, distinct from this connector; source of the Australian data-residency statement. · retrieved 2026-08-23
- MYOB Australia machine-readable site index (retrieved 2026-08-23). Source of the product tier list. · retrieved 2026-08-23
- Live OAuth posture check: anonymous request to returned 401 with
WWW-Authenticate: Bearer; RFC 9728 metadata at ; authorization server metadata at (2026-08-23). Control probes for unrelated paths on the same host returned empty 404s, so the descriptor is genuine rather than a catch-all. · retrieved 2026-08-23 - MYOB Developer Centre (retrieved 2026-08-23). No occurrence of any of the six tool names, "MCP" or "Model Context Protocol" anywhere on the developer portal. · retrieved 2026-08-23
- MYOB Business API v2 endpoint documentation (retrieved 2026-08-23, HTTP 200). This is the canonical path: the older
/api/accountright/v2/equivalents each returned HTTP 301 to it, which is why the two APIs are one surface. The v2 index renders its nav titles as the literal stringNone, so resource paths were counted from the six collection index pages instead. · retrieved 2026-08-23 - MYOB API payroll collection, listing eleven payroll resources (retrieved 2026-08-23). The
ABNOrTFNfield appears on ; we found no employee-level tax file number field and make no claim either way. · retrieved 2026-08-23 - MYOB API endpoint pages verifying
GET | PUT | POST | DELETE— · · · · (each retrieved 2026-08-23). We did not obtain or use a MYOB developer API key;https://api.myob.com/accountright/returns an unauthenticated error and was not called with credentials. · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshots dated 2026-08-23 and 2026-08-16 · retrieved 2026-08-23
- MYOB support — · Privacy — · Status
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Finance
- Developer
- MYOB
- Tools
- 6
- Domain
- mcp.myob.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.