CData Square Server

What it is

A local, read-only MCP server that exposes Square as a relational SQL model. It wraps CData's JDBC driver for Square, which presents the account's objects as tables, so an assistant can discover the schema and answer questions about live payments and merchant data with SELECT queries.

What you get

• The tables available in Square, returned as CSV with a header row — get_tables
• The columns on a chosen table, so a query uses real column names — get_columns
• A SQL SELECT executed against live Square data — run_query
• Tool names that start with the Prefix in your .prp file (square_ in the sample), so several CData servers can sit side by side
• 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

A Square account, plus CData's JDBC driver for Square downloaded and licensed separately — java -jar cdata.jdbc.square.jar --license takes your name, email and TRIAL or a license key. Java and Maven: mvn clean install builds the runnable JAR. Then a .prp file with the prefix, server name and version, the driver JAR path, the driver class cdata.jdbc.square.SquareDriver, and the JDBC connection string from the driver's connection-string utility, which opens a browser for OAuth. The client entry runs java with the JAR and the .prp path. Communication is over stdio, so client and server must be on the same machine. MIT licensed.

Setup effort

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

Tools you get

3 tools named in the project's documentation. Tool names start with the Prefix set in the .prp file, for example square_run_query. The build is read-only: square_run_query executes SQL SELECT only, although the documentation also promises writes.

Where it runs

Both documented setups run the server on your machine.