Skip to content

MCP User Guide

Setting Up RDLC to DevExpress Converter in Cursor

This guide shows you how to configure and use the RDLC to DevExpress converter with Cursor AI.

Important: Two Workspaces

This setup involves two separate workspaces:

  1. Converter Repository Workspace - Where you build and run the converter code

    • Clone/download the Rdlc.Repx.Converter repository
    • Build the MCP server
    • Run the conversion service

  2. Your Project Workspace - Where you use the converter

    • Configure MCP in Cursor
    • Convert your RDLC files
    • Work with your project code

Setup Steps

Step 1: Locate or Create MCP Configuration File

Location: Your Project Workspace (or global Cursor settings)

The MCP configuration file tells Cursor how to connect to the RDLC converter server.

Configuration file location:

C:\Users\YourUsername\.cursor\mcp.json

~/.cursor/mcp.json

If the file doesn't exist:

  1. Create the .cursor folder in your home directory (if it doesn't exist)
  2. Create a new file named mcp.json in that folder
  3. Add the configuration below

Step 2: Configure the MCP Server

Location: Your Project Workspace (editing mcp.json)

Add the following configuration to your mcp.json file:

{
  "mcpServers": {
    "rdlc-converter": {
      "command": "node",
      "args": ["/absolute/path/to/Rdlc.Repx.Converter/src/McpServer/dist/index.js"],
      "env": {
        "API_URL": "http://localhost:5000",
        "RULES_PATH": "/absolute/path/to/Rdlc.Repx.Converter/data/rules/mapping-rules.json",
        "MIGRATION_DOCS_PATH": "/absolute/path/to/Rdlc.Repx.Converter/internal-docs/ai-instructions/devexpress-migration",
        "MIGRATION_PROGRESS_PATH": "/absolute/path/to/YourProject/MIGRATION_PROGRESS.md"
      }
    }
  }
}

Important: Use Absolute Paths

Replace /absolute/path/to/Rdlc.Repx.Converter with the actual path to the Converter Repository Workspace (where you cloned/downloaded the converter code).

Examples:

  • Windows: C:/Repositories/Rdlc.Repx.Converter
  • macOS/Linux: /home/username/repositories/Rdlc.Repx.Converter

This is NOT your project workspace - it's the separate workspace where the converter code lives.

Configuration Parameters:

Parameter Description Required
command Node.js executable Yes
args Path to MCP server entry point (dist/index.js) Yes
API_URL Conversion API endpoint Yes (default: http://localhost:5000)
RULES_PATH Path to mapping rules JSON file Yes
MIGRATION_DOCS_PATH Path to migration documentation folder Yes (for migration)
MIGRATION_PROGRESS_PATH Path for migration progress tracker Yes (for migration)

Step 3: Build the MCP Server

Location: Converter Repository Workspace

Before using the converter, you need to build the MCP server in the Converter Repository Workspace:

# Navigate to the converter repository
cd /path/to/Rdlc.Repx.Converter

# Navigate to MCP server directory
cd src/McpServer

# Install dependencies
npm install

# Build
npm run build

This creates the dist/ folder that Cursor will run.

One-Time Setup

You only need to build the MCP server once (or after updates). This happens in the converter repository, not your project workspace.

Step 4: Start the Conversion Service

Location: Converter Repository Workspace

The MCP server needs the conversion API to be running. Start it in the Converter Repository Workspace:

# Navigate to the converter repository
cd /path/to/Rdlc.Repx.Converter

# Navigate to conversion service directory
cd src/ConversionService

# Start the service
dotnet run

Verify the service is running: 

# Optionally
curl http://localhost:5000/health

Keep It Running

Keep this terminal window open while using the converter. The service must be running for conversions to work.

This runs in the converter repository workspace, not your project workspace.

Step 5: Enable the MCP Server in Cursor

Location: Your Project Workspace

After updating mcp.json, open Cursor in Your Project Workspace and enable the MCP server:

  1. Open Cursor Settings (File → Preferences → Settings or Ctrl+, / Cmd+,)
  2. Navigate to Tools & MCP section
  3. Find the rdlc-converter server in the list
  4. Toggle it ON (or toggle OFF then ON to reload)

The MCP server will start automatically when enabled.

Verify Setup

To verify the MCP server is configured correctly, open Cursor in your project workspace and ask:

"What MCP tools are available?"

You should see convert_rdlc_to_devexpress and migration tools in the list.

Reloading Configuration

If you make changes to mcp.json after the server is already running, toggle the server OFF then ON in the Tools & MCP settings to reload the configuration.

Verifying Your Setup

To verify everything is working correctly:

Check MCP tools are available:

"What MCP tools are available?"

You should see tools like convert_rdlc_to_devexpress, get_migration_prompt, etc.

Try the getting started guide: 

"How do I get started with the DevExpress converter?"

The AI will present your options and guide you to the right documentation.

Next Steps

Now that your MCP server is set up and connected, you can use it for:

Option 1: Convert Individual RDLC Files

Convert one or more RDLC reports to DevExpress REPX format.

📖 See: RDLC to DevExpress Conversion Guide

Quick start: 

"Convert this RDLC report to DevExpress format"

Option 2: Full ValSuite Project Migration

Migrate your entire ValSuite project with the 20-prompt guided migration.

📖 See: DevExpress Migration Guide

Quick start: 

"Show me the DevExpress migration overview"

Troubleshooting Setup

MCP Server Not Showing in Cursor

  1. Check mcp.json syntax - Ensure valid JSON format
  2. Verify paths are absolute - Relative paths won't work
  3. Check file permissions - Ensure dist/index.js is readable
  4. Restart Cursor - Sometimes needed after configuration changes

Conversion Service Not Starting

  1. Check .NET is installed: dotnet --version
  2. Verify you're in the right directory: src/ConversionService
  3. Check port 5000 is available: netstat -an | grep 5000
  4. Review error messages in the terminal

MCP Server Connection Issues

  1. Check the conversion service is running (Step 4)
  2. Verify API_URL in mcp.json points to http://localhost:5000
  3. Check firewall settings - Ensure localhost connections allowed
  4. Review MCP server logs in Cursor's output panel

See Also

Usage Guides

Reference

Last Updated: December 18, 2025