home / mcp / shipstation mcp server
This read-only MCP Server allows you to connect to ShipStation data from Claude Desktop through CData JDBC Drivers. For full CRUD support, check out the first managed MCP platform: CData Connect AI (https://www.cdata.com/ai/).
Configuration
View docs{
"mcpServers": {
"cdatasoftware-shipstation-mcp-server-by-cdata": {
"command": "java",
"args": [
"-jar",
"/PATH/TO/CDataMCP-jar-with-dependencies.jar",
"/PATH/TO/shipstation.prp"
]
}
}
}You can run a local, read-only MCP server that exposes ShipStation data through a simple MCP interface. This lets you ask natural language questions about live ShipStation data and get structured, up-to-date results without writing SQL.
You will run a local MCP server that speaks the MCP protocol over stdio. Start it on the same machine as your MCP client (for example Claude Desktop) and point your client at the server. Once running, you can ask questions like how many open tickets you have, what the current status of a shipment is, or which orders match specific criteria. The server translates your natural language requests into the underlying data operations and returns results in a friendly format.
To use the server, ensure your MCP client is configured to launch the Java process that hosts the MCP server and passes the path to the server configuration file. The standard startup flow is to run a Java command that loads the server and the specific ShipStation.prp configuration.
# prerequisites
- Java Runtime Environment (JRE) or JDK 8+
- Maven (for building the MCP server)
# 1) Clone the project
git clone https://github.com/cdatasoftware/shipstation-mcp-server-by-cdata.git
cd shipstation-mcp-server-by-cdata
# 2) Build the server
mvn clean install
# This creates the JAR: CDataMCP-jar-with-dependencies.jar
# 3) Prepare the JDBC driver and configuration
# You will install and license the CData JDBC Driver for ShipStation separately
# Follow the provided steps to install and license the driver, and create a .prp file (e.g. shipstation.prp)
# 4) Run the MCP server (example)
java -jar /PATH/TO/CDataMCP-jar-with-dependencies.jar /PATH/TO/shipstation.prp
```} ,{Notes and tips: - The server is designed to be run locally for read-only access to ShipStation data. If you need remote access or write capabilities, explore the full MCP server options provided by the vendor. - Keep your ShipStation credentials and OAuth tokens secure. Do not expose the .prp file or the JDBC connection string to untrusted clients. - If your MCP client cannot discover the server, make sure the Java process is started with the correct path to the .prp file and that the client is configured to launch the same server instance.
Configuration is driven by a .prp file that contains the JDBC connection details, driver information, and the list of accessible tables. The .prp includes keys such as Prefix, ServerName, ServerVersion, DriverPath, DriverClass, and JdbcUrl. Use the exact formatting shown in the example to ensure the MCP server can load your ShipStation data.
Security considerations: - Run the MCP server on a trusted machine and restrict access to the local network. - Treat the .prp contents and any OAuth tokens as sensitive data. - Regularly rotate credentials and monitor access to the MCP endpoint.
If you cannot see the MCP server from your client, fully quit the client and relaunch it so it re-scan discovers new local servers. If data cannot be retrieved, verify the JDBC connection string, ensure the driver is licensed, and confirm the .prp path used by the server matches the one in your client configuration. If you run into issues with the MCP server itself, check that the Java process is running with the correct arguments and that the classpath includes the necessary dependencies.
License and support: This MCP server setup assumes you have licensed the CData JDBC Driver for ShipStation according to the licensing steps outlined in the setup. If you encounter licensing issues, contact CData Support for assistance.
The MCP server provides tools that map to the ShipStation data exposed via the JDBC driver. Typical tools include: - shipstation_get_tables – Retrieves the list of accessible data tables. - shipstation_get_columns – Retrieves the columns available in a given table. - shipstation_run_query – Executes a SQL SELECT query against the accessible data.
Ask questions like: - Show me all open ShipStation tickets and their statuses. - What is the shipment status distribution for orders in the last 7 days? - List shipments that are overdue or delayed and their associated orders.
If you are scripting interactions with the MCP server, you can use the provided tools in JSON-RPC 2.0 format. For example, you can request the list of tables, their columns, or run a query by calling the corresponding tool with the appropriate arguments.
Retrieves a list of tables available in the ShipStation data source. The output is a CSV with column headers as the first line.
Retrieves a list of columns for a specific table. The output is CSV with column headers on the first line.
Executes a SQL SELECT query against the ShipStation data exposed through the MCP server.