myobaccountright_get_tablesLABSCO SUMMARY
Read-only by construction.
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. How much of the ledger an assistant can see is set by the account you connect with — the Tables entry in the connection file does not narrow what the tools can query.
What it is
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.
What you get
- 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
Tablessetting that only picks which tables also get a ready-made description (blank means none); it does not limit what the tools can list or query, so limit the connection or the account it signs in with
Requirements
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.
Setup effort
Build from source — clone the repository, then point your client at the binary
USE CASES
Answering a finance question without opening MYOB
Ask in plain language; the client discovers the tables and columns it needs, then runs one SELECT against live data.
Learning what the driver actually exposes
List the tables, then read the columns of the ones that look relevant, so a query gets written against real field names rather than guesses.
3 tools
Listed in project docs. Your client may show a different list.
myobaccountright_get_columnsmyobaccountright_run_queryBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation. Tool names start with the Prefix in the .prp file, so the README's Prefix=myobaccountright gives myobaccountright_get_tables, myobaccountright_get_columns and myobaccountright_run_query. All three only read: run_query executes SELECT, even though one sentence in the README promises writes.
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
Clone the repository, then point your client at the binary. This one is built from source rather than installed with a single command.
Server setup
git clone https://github.com/cdatasoftware/myob-accountright-mcp-server-by-cdata.git
cd myob-accountright-mcp-server-by-cdata
mvn clean installDownload and install the CData JDBC Driver for MYOB AccountRight from https://www.cdata.com/drivers/myobaccountright/download/jdbc
License the driver: from the driver install's lib folder run java -jar cdata.jdbc.myobaccountright.jar --license, then enter your name, email, and "TRIAL" (or your license key)
Build the connection string: run java -jar cdata.jdbc.myobaccountright.jar to open the Connection String utility, click "Test Connection" (browser OAuth if the source needs it), and copy the connection string
Create myob-accountright.prp with:
Prefix=myobaccountright
ServerName=CDataMYOBAccountRight
ServerVersion=1.0
DriverPath=<YOUR_DRIVER_PATH>
DriverClass=cdata.jdbc.myobaccountright.MYOBAccountRightDriver
JdbcUrl=<YOUR_JDBC_URL>
Tables=Tables only picks which tables also get a ready-made description for your assistant, and empty means none; the server can still list and query every table your connection string reaches, so to keep data out of reach, limit that connection or the account it signs in with.
Add the mcpServers entry (block below) to claude_desktop_config.json, then fully quit and re-open the client
MCP Clients
Claude Desktop — Windows, macOS, Linux
{
"mcpServers": {
"myob-accountright": {
"command": "<YOUR_PATH_TO_JAVA>",
"args": [
"-jar",
"<YOUR_PATH_TO_CDATA_MCP_JAR_WITH>",
"<YOUR_PATH_TO_MYOB_ACCOUNTRIGHT>"
]
}
}
}