The CData Sync MCP Server exposes CData Sync's REST API through the MCP toolset, enabling automated management of connections, jobs, tasks, users, and related resources via either a local stdio transport (for desktop usage with Claude Desktop) or a streamable HTTP transport (for remote or web-based usage). The server consolidates 20+ MCP tools into a single interface and provides real-time notifications via Server-Sent Events. To get started, run the server in the desired transport mode and configure your MCP clients to connect using the provided endpoints. The included tools cover core areas such as reading and writing connections, managing synchronization jobs, handling tasks and transformations, user management, and monitoring history and logs. You can also enable dual transport during development to validate both local and remote workflows.

Prerequisites:

• Node.js 18+
• A running CData Sync instance
• Internet access to install dependencies (npm)

Step-by-step installation:

1. Clone the repository git clone https://github.com/CDataSoftware/cdata-sync-mcp-server.git cd cdata-sync-mcp-server

2. Install dependencies npm install

3. Build the project npm run build

4. Configure environment variables (example)

   Copy the example environment file

   cp .env.example .env

   Edit with your CData Sync details

   CDATA_BASE_URL="http://localhost:8181/api.rsc" CDATA_AUTH_TOKEN="your-auth-token" CDATA_WORKSPACE="your-workspace-uuid" # Optional MCP_TRANSPORT_MODE="both" # stdio, http, or both

5. Run the server (example for stdio only) npm run start:stdio

6. Optional: Run the HTTP transport (remote server) npm run start:http

7. Development utilities npm run dev:both # start both transports npm run test # run tests (if provided)

Environment variables: The server relies on CDATA_BASE_URL, CDATA_AUTH_TOKEN (or CDATA_USERNAME/CDATA_PASSWORD for basic auth), and optional CDATA_WORKSPACE to scope operations. For local development with Claude Desktop, MCP_TRANSPORT_MODE should be set to stdio. For remote deployments, use http or both transport modes. If you encounter connection issues, ensure the CData Sync instance is reachable at the base URL and that the auth token (or credentials) is valid. The server supports real-time updates via SSE; ensure DISABLE_SSE is not set or is set to false to receive notifications. When deploying in Docker/Kubernetes, map environment variables accordingly and expose the required endpoints for the HTTP transport.