LabscoMCP early access ↗
CDataSoftwareMCP SERVER

Intacct MCP Server by CData

Query live Intacct accounting data in plain English through CData's JDBC driver — read-only.

by CDataSoftware ↗SaaS-to-SQL ConnectorsCommunity

LABSCO SUMMARY

Read-only is the right default for the ledger.

Accounting data is exactly where you do not want an assistant holding a write handle, and this server does not have one: table discovery plus a SELECT. That makes it usable for the questions finance actually asks between close cycles — what has been posted, against which dimension, since when — while leaving the system of record untouched. Getting there takes a Maven build, a licensed driver and a property file.

What it is

A local, read-only bridge between an assistant and Intacct. CData's JDBC driver exposes Intacct as relational SQL models; this server wraps the driver so a model can discover the tables and query them, and you can ask in plain language instead of writing SQL. It runs over stdio, so the client has to be on the same machine.

What you get

  • get_tables lists the tables the driver exposes, returned as CSV with a header row
  • get_columns lists the columns on one of those tables, in the same CSV shape
  • run_query executes a SQL SELECT against live Intacct data
  • Tool names carry the prefix you set in the property file — the sample config uses Prefix=sageintacct
  • A Tables setting 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

Java and Maven: mvn clean install builds CDataMCP-jar-with-dependencies.jar. Separately install the CData JDBC Driver for Intacct and license it by running java -jar cdata.jdbc.sageintacct.jar --license, entering TRIAL or a license key. Build the connection string with the same jar, authenticating in the browser if the source uses OAuth, then write a .prp file naming the driver path, the driver class cdata.jdbc.sageintacct.SageIntacctDriver and that JDBC URL. Point your client at java -jar with the built jar and the .prp file.

Setup effort

Build from source — clone the repository, then point your client at the binary