CData Sync MCP Server
A comprehensive Model Context Protocol (MCP) server for with . This server exposes CData Sync's REST API as MCP tools, enabling AI assistants like Claude to manage data synchronization jobs, connections, and ETL operations.
Power your agent
Install from the publisher. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
No packaged release in the registry yet. Follow the repository README.
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
A comprehensive Model Context Protocol (MCP) server for with . This server exposes CData Sync's REST API as MCP tools, enabling AI assistants like Claude to manage data synchronization jobs, connections, and ETL operations.
MCP server for CData Sync - enables natural language and/or AI assistants to manage ETL jobs, data connections, and transformations via Model Context Protocol
Transport Options:
Clone the repository
git clone https://github.com/CDataSoftware/cdata-sync-mcp-server.git
cd cdata-sync-mcp-server
Install dependencies
npm install
Build the project
npm run build
Configure environment variables
# 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: scope operations to specific workspace
MCP_TRANSPORT_MODE="both" # stdio, http, or both
The stdio transport is designed for local desktop usage with the Claude Desktop app. This is the recommended approach for individual developers.
Configuration for Claude Desktop:
{
"mcpServers": {
"cdata-sync-server": {
"command": "node",
"args": ["/absolute/path/to/cdata-sync-mcp-server/dist/index.js"],
"env": {
"MCP_TRANSPORT_MODE": "stdio",
"CDATA_AUTH_TOKEN": "your-token-here",
"CDATA_BASE_URL": "http://localhost:8181/api.rsc",
"CDATA_WORKSPACE": "your-workspace-uuid-here",
"DISABLE_SSE": "true"
}
}
}
}
Start stdio-only server:
npm run start:stdio
The HTTP transport is designed for server deployments where the MCP server runs on a remote machine and accepts API requests. This is ideal for:
Start HTTP-only server:
npm run start:http
Available endpoints:
GET /mcp/v1/info - Server and protocol informationGET /mcp/v1/health - Health checkPOST /mcp/v1/message - Send MCP requestsGET /mcp/v1/stream - Server-Sent Events for real-time updatesExample HTTP client usage:
// Connect to the server
const client = new MCPStreamableHttpClient('http://your-server:3000/mcp/v1');
await client.connect();
// List available tools
const tools = await client.listTools();
// Call a tool
const connections = await client.callTool('read_connections', {
action: 'list',
top: 5
});
// Set up real-time monitoring
client.onNotification = (method, params) => {
console.log('Notification:', method, params);
};
For development and testing, you can run both transports simultaneously:
npm run start:both
This is useful for testing both desktop and server scenarios during development.
read_connections - List, count, get details, or test connectionswrite_connections - Create, update, or delete connectionsget_connection_tables - List tables in connectionget_table_columns - Get table schema informationread_jobs - List, count, get details, status, history, or logswrite_jobs - Create, update, or delete jobsexecute_job - Run a sync job immediatelycancel_job - Stop running jobexecute_query - Run custom SQL queriesread_tasks - List, count, or get task detailswrite_tasks - Create, update, or delete tasksread_transformations - List, count, or get transformation detailswrite_transformations - Create, update, or delete transformationsread_users - List, count, or get user detailswrite_users - Create or update usersread_requests - List, count, or get request log detailswrite_requests - Delete request logsread_history - List or count execution history recordsread_certificates - List certificateswrite_certificates - Create certificatesconfigure_sync_server - Get or update server configurationAll read/write tools use an action parameter to specify the operation:
Example: Reading connections
{
"tool": "read_connections",
"arguments": {
"action": "list",
"filter": "contains(Name,'prod')",
"top": 10
}
}
Example: Creating a connection
{
"tool": "write_connections",
"arguments": {
"action": "create",
"name": "MyDatabase",
"providerName": "System.Data.SqlClient",
"connectionString": "Server=localhost;Database=test;"
}
}
The HTTP transport provides real-time notifications for:
// Monitor all server events
const eventSource = new EventSource('http://localhost:3000/mcp/v1/stream');
eventSource.onmessage = (event) => {
const message = JSON.parse(event.data);
if (message.method === 'notifications/job_executed') {
console.log('Job completed:', message.params);
}
};
# Start in development mode with both transports
npm run dev:both
# Start with stdio only
npm run dev:stdio
# Start with HTTP only
npm run dev:http
# Type checking
npm run typecheck
# Linting
npm run lint
npm run lint:fix
# Testing
npm test
npm run test:watch
npm run test:coverage
# Build image
docker build -t cdata-sync-mcp-server .
# Run with stdio transport
docker run -e CDATA_AUTH_TOKEN=your-token cdata-sync-mcp-server
# Run with HTTP transport
docker run -p 3000:3000 -e MCP_TRANSPORT_MODE=http -e CDATA_AUTH_TOKEN=your-token cdata-sync-mcp-server
# Start with Docker Compose
docker-compose up -d cdata-sync-mcp-both
# Deploy to Kubernetes
kubectl apply -f k8s/
# Install as systemd service
sudo cp cdata-sync-mcp.service /etc/systemd/system/
sudo systemctl enable cdata-sync-mcp
sudo systemctl start cdata-sync-mcp
GET /mcp/v1/info
{
"protocol": "Model Context Protocol",
"version": "2025-03-26",
"transport": "streamable-http",
"endpoints": {
"message": "http://localhost:3000/mcp/v1/message",
"stream": "http://localhost:3000/mcp/v1/stream"
}
}
GET /mcp/v1/health
{
"status": "healthy",
"transport": "streamable-http",
"timestamp": "2024-01-15T10:30:00Z",
"pendingRequests": 0,
"bufferedMessages": 0
}
POST /mcp/v1/message
{
"jsonrpc": "2.0",
"id": "1",
"method": "tools/call",
"params": {
"name": "read_connections",
"arguments": {
"action": "list",
"top": 5
}
}
}
GET /mcp/v1/stream
Server-Sent Events stream providing real-time notifications:
data: {"jsonrpc":"2.0","method":"notifications/tool_execution","params":{"tool":"read_connections","timestamp":"2024-01-15T10:30:00Z"}}
data: {"jsonrpc":"2.0","method":"notifications/job_executed","params":{"jobName":"TestJob","result":"success","timestamp":"2024-01-15T10:31:00Z"}}
# Run all tests
npm test
# Run with coverage
npm run test:coverage
# Watch mode for development
npm run test:watch
src/
├── __tests__/
│ ├── services/ # Service unit tests
│ ├── transport/ # Transport tests
│ ├── integration/ # Integration tests
│ └── utils/ # Utility tests
git checkout -b feature/amazing-feature)git commit -m 'Add some amazing feature')git push origin feature/amazing-feature)This project is licensed under the MIT License - see the LICENSE file for details.
Built with ❤️ for the MCP ecosystem
MCP server for CData Sync - enables natural language and/or AI assistants to manage ETL jobs, data connections, and transformations via Model Context Protocol
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Cdata Sync runs locally over stdio.
Last checked 2026-10-28. MCP server for CData Sync - enables natural language and/or AI assistants to manage ETL jobs, data connections, and transformations via Model Context Protocol