RDRS MCP Server
Enables natural language interaction with Rocket Data Replicate and Sync (RDRS) through AI assistants. Supports management of agents, data sources, processes, and replication tasks.
README
RDRS MCP Server
Model Context Protocol (MCP) server for Rocket Data Replicate and Sync (RDRS).
Overview
This MCP server provides a natural language interface to interact with RDRS through AI assistants like GitHub Copilot, Claude Desktop, and Cline. It connects to your local RDRS installation and exposes comprehensive tools for managing agents, data sources, processes, and replication tasks.
Prerequisites
- RDRS 7.0+ installed and running locally
- Python 3.8+
- Java 8+ (required by RDRS)
- RDRS REST API running (default:
http://localhost:8080)
Installation
1. Clone the Repository
git clone https://github.com/myunussheikhRS/rdrs_MCP.git
cd rdrs_MCP
2. Set Up Python Environment
# Create virtual environment
python -m venv .venv
# Activate virtual environment
# Windows:
.venv\Scripts\activate
# Linux/Mac:
source .venv/bin/activate
# Install dependencies
pip install -r requirements.txt
3. Configure MCP Client
GitHub Copilot (VS Code)
Add to %APPDATA%\Code\User\globalStorage\github.copilot-chat\mcp.json:
{
"mcpServers": {
"rdrs": {
"command": "python",
"args": [
"c:\\path\\to\\rdrs_MCP\\rdrs_server_fixed.py"
],
"env": {
"RDRS_URL": "http://127.0.0.1:8080"
}
}
}
}
Claude Desktop
Add to %APPDATA%\Claude\claude_desktop_config.json (Windows) or ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):
{
"mcpServers": {
"rdrs": {
"command": "python",
"args": [
"/path/to/rdrs_MCP/rdrs_server_fixed.py"
],
"env": {
"RDRS_URL": "http://127.0.0.1:8080"
}
}
}
}
4. Restart Your MCP Client
Restart GitHub Copilot/Claude Desktop to load the RDRS MCP server.
Features
Agent Management
- Get active agents
- List defined agents
- Add/update/delete agents
- Test agent connectivity
Data Source Management
- List data sources
- Add/configure data sources
- Test data source connectivity
- Support for Oracle, DB2, PostgreSQL, MySQL, MSSQL, and more
Process Management
- List active/defined/terminated processes
- Start/stop processes
- Get process statistics and latency
- Monitor process health
Health Check
- System prerequisites validation
- Java installation check
- Port availability verification
- RDRS connectivity test
- Database environment detection
Usage Examples
Once configured, interact with RDRS through natural language:
"Get active RDRS agents"
"List all defined processes"
"Show me the health check status"
"Start process OrderSync"
"Get statistics for process CustomerReplication"
Available Tools
The server exposes 50+ tools including:
rdrs_get_active_agents()- Get all active agentsrdrs_list_defined_processes()- List process definitionsrdrs_start_process(name)- Start a processrdrs_get_process_statistics(name, pid)- Get process statsrdrs_health_check()- Comprehensive system check- And many more...
Configuration
Environment Variables
RDRS_URL- RDRS REST API endpoint (default:http://127.0.0.1:8080)
RDRS Ports
- 4135 - RDRS Agent communication port
- 8080 - RDRS REST API port (configurable)
Security
⚠️ Important: This MCP server is designed for local use only. It connects to your local RDRS installation and should NOT be exposed publicly without proper authentication and security measures.
Troubleshooting
MCP Server Not Connecting
- Ensure RDRS is running: Check Task Manager for
tcvm.exe - Verify RDRS_URL is correct
- Check firewall settings for port 4135/8080
- Run health check: Ask "Run RDRS health check"
No Active Agents
- Verify RDRS agent is started
- Check agent configuration in RDRS
- Ensure structure repository is accessible
Connection Errors
- Verify RDRS REST API is enabled
- Check
RDRS_URLenvironment variable - Ensure no SSL certificate issues
Documentation
Contributing
Contributions are welcome! Please feel free to submit issues or pull requests.
License
Copyright © 2025 Rocket Software, Inc.
Support
For RDRS-related issues, contact Rocket Software support. For MCP server issues, please open a GitHub issue.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.