myob-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key. Get one at https://cotlet.dev/app. Without it, tool calls return: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app". |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
MYOB through Cotlet.dev. Call myob_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| myob_guideA | How to work in MYOB (invoices, bills and payments): its screens and the sign-in link. Call this first. |
| myob_statusA | Check that your Cotlet.dev account and MYOB are ready: account, credits and MYOB connection. |
| myob_openB | Open a MYOB page in your signed-in Cloud Browser (default https://myob.com) to work with invoices, bills and payments. |
| myob_readA | Read the current MYOB page: its text and numbered buttons, links and fields. |
| myob_clickC | Click a numbered element on the current MYOB page. |
| myob_typeB | Type text into a numbered field on the current MYOB page. |
| myob_closeA | Close the MYOB browser session when the work is done, so credits stop running. |
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 7 tools
Each tool maps to a distinct action in a browser-automation lifecycle: guide/status are pre-flight, open/read/click/type operate on the page, close tears down. The only mild overlap is myob_guide vs myob_status, but the descriptions clearly separate documentation from readiness checking.
All seven tools follow the same myob_<verb> snake_case pattern (read, click, type, close, guide, status, open). No mixed conventions or stray casing.
Seven tools is well within the ideal 3-15 range and every tool earns its place in the open-work-close loop. Nothing feels redundant or padded.
The surface covers the full session lifecycle and core interaction primitives (open, read, click, type, close) plus onboarding and status. Minor gaps remain for richer page interaction such as selecting dropdown options, scrolling, or waiting for load, which agents may have to work around.