ShipStation MCP Server by CData

shipstation-mcp-server-by-cdata

CData's Model Context Protocol (MCP) Server for ShipStation

Purpose

We created this read-only MCP Server to allow LLMs (like Claude Desktop) to query live data ShipStation supported by the CData JDBC Driver for ShipStation.

CData JDBC Driver connects to ShipStation by exposing them as relational SQL models.

This server wraps that driver and makes ShipStation data available through a simple MCP interface, so LLMs can retrieve live information by asking natural language questions — no SQL required.

Setup Guide

1. Clone the repository:

      git clone https://github.com/cdatasoftware/shipstation-mcp-server-by-cdata.git
      cd shipstation-mcp-server-by-cdata

1. Build the server:

      mvn clean install

This creates the JAR file: CDataMCP-jar-with-dependencies.jar

1. Download and install the CData JDBC Driver for {source}:
2. License the CData JDBC Driver:

* Navigate to the lib folder in the installation directory, typically: * (Windows) C:\Program Files\CData\CData JDBC Driver for ShipStation\ * (Mac/Linux) /Applications/CData JDBC Driver for ShipStation/ * Run the command java -jar cdata.jdbc.shipstation.jar --license * Enter your name, email, and "TRIAL" (or your license key).

1. Configure your connection to the data source (Salesforce as an example):

* Run the command java -jar cdata.jdbc.shipstation.jar to open the Connection String utility.

* Configure the connection string and click "Test Connection" > Note: If the data sources uses OAuth, you will need to authenticate in your browser. * Once successful, copy the connection string for use later.

1. Create a .prp file for your JDBC connection (e.g. shipstation.prp) using the following properties and format:

* Prefix - a prefix to be used for the tools exposed * ServerName - a name for your server * ServerVersion - a version for your server * DriverPath - the full path to the JAR file for your JDBC driver * DriverClass - the name of the JDBC Driver Class (e.g. cdata.jdbc.shipstation.ShipStationDriver) * JdbcUrl - the JDBC connection string to use with the CData JDBC Driver to connect to your data (copied from above) * Tables - leave blank to access all data, otherwise you can explicitly declare the tables you wish to create access for

      Prefix=shipstation
      ServerName=CDataShipStation
      ServerVersion=1.0
      DriverPath=PATH\TO\cdata.jdbc.shipstation.jar
      DriverClass=cdata.jdbc.shipstation.ShipStationDriver
      JdbcUrl=jdbc:shipstation:InitiateOAuth=GETANDREFRESH;
      Tables=

Using the Server with Claude Desktop

1. Create the config file for Claude Desktop ( claude_desktop_config.json) to add the new MCP server, using the format below. If the file already exists, add the entry to the mcpServers in the config file.

Windows

      {
        "mcpServers": {
          "{classname_dash}": {
            "command": "PATH\\TO\\java.exe",
            "args": [
              "-jar",
              "PATH\\TO\\CDataMCP-jar-with-dependencies.jar",
              "PATH\\TO\\shipstation.prp"
            ]
          },
          ...
        }
      }

Linux/Mac

      {
        "mcpServers": {
          "{classname_dash}": {
            "command": "/PATH/TO/java",
            "args": [
              "-jar",
              "/PATH/TO/CDataMCP-jar-with-dependencies.jar",
              "/PATH/TO/shipstation.prp"
            ]
          },
          ...
        }
      }

If needed, copy the config file to the appropriate directory (Claude Desktop as the example). Windows

      cp C:\PATH\TO\claude_desktop_config.json %APPDATA%\Claude\claude_desktop_config.json

Linux/Mac

      cp /PATH/TO/claude_desktop_config.json /Users/{user}/Library/Application\ Support/Claude/claude_desktop_config.json'

1. Run or refresh your client (Claude Desktop).

Note: You may need to fully exit or quit your Claude Desktop client and re-open it for the MCP Servers to appear.

Running the Server

1. Run the follow the command to run the MCP Server on its own

      java -jar /PATH/TO/CDataMCP-jar-with-dependencies.jar /PATH/TO/Salesforce.prp
> **Note:** The server uses `stdio` so can only be used with clients that run on the same machine as the server.
## Usage Details
Once the MCP Server is configured, the AI client will be able to use the built-in tools to read, write, update, and delete the underlying data. In general, you do not need to call the tools explicitly. Simply ask the client to answer questions about the underlying data system. For example:
* "What is the correlation between my closed won opportunities and the account industry?"
* "How many open tickets do I have in the SUPPORT project?"
* "Can you tell me what calendar events I have today?"

The list of tools available and their descriptions follow:
### Tools & Descriptions
In the definitions below, `{servername}` refers to the name of the MCP Server in the config file (e.g. `{classname_dash}` above).
* `{servername}_get_tables` - Retrieves a list of tables available in the data source. Use the `{servername}_get_columns` tool to list available columns on a table. The output of the tool will be returned in CSV format, with the first line containing column headers.
* `{servername}_get_columns` - Retrieves a list of columns for a table. Use the `{servername}_get_tables` tool to get a list of available tables. The output of the tool will be returned in CSV format, with the first line containing column headers.
* `{servername}_run_query` - Execute a SQL SELECT query

## JSON-RPC Request Examples
If you are scripting out the requests sent to the MCP Server instead of using an AI Client (e.g. Claude), then you can refer to the JSON payload examples below – following the JSON-RPC 2.0 specification - when calling the available tools. 

#### source_get_tables

{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "source_get_tables", "arguments": {} } }

#### source_get_columns

{ "jsonrpc": "2.0", "id": 2, "method": "tools/call", "params": { "name": "source_get_columns", "arguments": { "table": "Account" } } }

#### source_run_query

{ "jsonrpc": "2.0", "id": 3, "method": "tools/call", "params": { "name": "source_run_query", "arguments": { "sql": "SELECT * FROM [Account] WHERE [IsDeleted] = true" } } }

## Troubleshooting
1. If you cannot see your CData MCP Server in Claude Desktop, be sure that you have fully quit Claude Desktop (Windows: use the Task Manager, Mac: use the Activity Monitor)
2. If Claude Desktop is unable to retrieve data, be sure that you have configured your connection properly. Use the Connection String builder to create the connection string (see above) and copy the connection string into the property (.prp) file.
3. If you are having trouble connecting to your data source, contact the [CData Support Team](https://www.cdata.com/support/submit.aspx).
4. If you are having trouble using the MCP server, or have any other feedback, join the [CData Community](https://community.cdata.com).

## License
This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the [LICENSE](./LICENSE) file in the project repository.

## All Supported Sources

AccessAct CRMAct-OnActive Directory
ActiveCampaignAcumaticaAdobe AnalyticsAdobe Commerce
ADPAirtableAlloyDBAmazon Athena
Amazon DynamoDBAmazon MarketplaceAmazon S3Asana
Authorize.NetAvalara AvaTaxAvroAzure Active Directory
Azure Analysis ServicesAzure Data CatalogAzure Data Lake StorageAzure DevOps
Azure SynapseAzure TableBasecampBigCommerce
BigQueryBing AdsBing SearchBitbucket
Blackbaud FE NXTBoxBullhorn CRMCassandra
CertiniaCloudantCockroachDBConfluence
Cosmos DBCouchbaseCouchDBCSV
CventDatabricksDB2DocuSign
DropboxDynamics 365Dynamics 365 Business CentralDynamics CRM
Dynamics GPDynamics NAVeBayeBay Analytics
ElasticsearchEmailEnterpriseDBEpicor Kinetic
Exact OnlineExcelExcel OnlineFacebook
Facebook AdsFHIRFreshdeskFTP
GitHubGmailGoogle Ad ManagerGoogle Ads
Google AnalyticsGoogle CalendarGoogle Campaign Manager 360Google Cloud Storage
Google ContactsGoogle Data CatalogGoogle DirectoryGoogle Drive
Google SearchGoogle SheetsGoogle SpannerGraphQL
GreenhouseGreenplumHarperDBHBase
HCL DominoHDFSHighriseHive
HubDBHubSpotIBM Cloud Data EngineIBM Cloud Object Storage
IBM InformixImpalaInstagramJDBC-ODBC Bridge
JiraJira AssetsJira Service ManagementJSON
KafkaKintoneLDAPLinkedIn
LinkedIn AdsMailChimpMariaDBMarketo
MarkLogicMicrosoft DataverseMicrosoft Entra IDMicrosoft Exchange
Microsoft OneDriveMicrosoft PlannerMicrosoft ProjectMicrosoft Teams
Monday.comMongoDBMYOB AccountRightMySQL
nCinoNeo4JNetSuiteOData
OdooOffice 365OktaOneNote
OracleOracle EloquaOracle Financials CloudOracle HCM Cloud
Oracle SalesOracle SCMOracle Service CloudOutreach.io
ParquetPaylocityPayPalPhoenix
PingOnePinterestPipedrivePostgreSQL
Power BI XMLAPrestoQuickbaseQuickBooks
QuickBooks OnlineQuickBooks TimeRaisers Edge NXTReckon
Reckon Accounts HostedRedisRedshiftREST
RSSSage 200Sage 300Sage 50 UK
Sage Cloud AccountingSage IntacctSalesforceSalesforce Data Cloud
Salesforce Financial Service CloudSalesforce MarketingSalesforce Marketing Cloud Account EngagementSalesforce Pardot
SalesloftSAPSAP Ariba ProcurementSAP Ariba Source
SAP Business OneSAP BusinessObjects BISAP ByDesignSAP Concur
SAP FieldglassSAP HANASAP HANA XS AdvancedSAP Hybris C4C
SAP Netweaver GatewaySAP SuccessFactorsSAS Data SetsSAS xpt
SendGridServiceNowSFTPSharePoint
SharePoint Excel ServicesShipStationShopifySingleStore
SlackSmartsheetSnapchat AdsSnowflake
SparkSplunkSQL Analysis ServicesSQL Server
SquareStripeSugar CRMSuiteCRM
SurveyMonkeySybaseSybase IQTableau CRM Analytics
TallyTaxJarTeradataTier1
TigerGraphTrelloTrinoTwilio
TwitterTwitter AdsVeeva CRMVeeva Vault
Wave FinancialWooCommerceWordPressWorkday
xBaseXeroXMLYouTube Analytics
ZendeskZoho BooksZoho CreatorZoho CRM
Zoho InventoryZoho ProjectsZuora... Dozens More