This build is deliberately the reading half of CData's stack — the write, update and delete path lives in their paid MCP server, and the remote option is a separate managed product. What makes the local build worth the setup is the `Tables` entry in the connection file: you decide up front how much of the ledger an assistant can see, before it ever connects.
A local, read-only MCP server from CData that wraps the CData JDBC Driver for MYOB AccountRight. The driver presents MYOB AccountRight as relational SQL models; the server turns those models into three tools, so a client can ask questions about live accounting data without anyone writing SQL by hand.
- The list of tables the driver exposes for your MYOB AccountRight connection, returned as CSV with a header row — `myobaccountright_get_tables`
- Column listings for any of those tables, again as CSV with headers — `myobaccountright_get_columns`
- SQL SELECT execution against the live connection — `myobaccountright_run_query`
- A `Tables` entry in the connection file that limits which tables are exposed at all, if you do not want the whole account reachable
A licensed CData JDBC Driver for MYOB AccountRight — run `java -jar cdata.jdbc.myobaccountright.jar --license` and enter TRIAL or your key. Java and Maven, since the server is built with `mvn clean install` into CDataMCP-jar-with-dependencies.jar. A `.prp` file carrying Prefix, ServerName, ServerVersion, DriverPath, DriverClass and JdbcUrl, passed as the jar's argument. MYOB AccountRight uses OAuth, so the first connection is authenticated in a browser. Transport is stdio, so the client must run on the same machine.
Build from source — clone the repository and build it, then point your client at the binary