HFSQL to n8n WinDev MCP Server for Railway

A Model Context Protocol (MCP) server that enables communication between HFSQL databases (used in WinDev) and n8n workflow automation platform.

Features

• Connect to HFSQL databases via ODBC
• List tables in HFSQL databases
• Describe table structures
• Query data from HFSQL tables
• Migrate data to n8n workflows
• Export query results to JSON

Installation

# Install globally
npm install -g hfsql-n8n-windev-mcp-server-railway

# Or use with npx
npx hfsql-n8n-windev-mcp-server-railway

Prerequisites

• Node.js 14 or higher
• ODBC drivers for HFSQL installed on your system
• n8n instance (if using migration features)

Usage

As an MCP Server for Claude

1. Install the package globally:

   npm install -g hfsql-n8n-windev-mcp-server-railway

2. Add the server to your Claude MCP configuration:

{
  "mcpServers": {
  "hfsql-n8n-windev-railway": {
    "command": "hfsql-n8n-windev-mcp-railway",
      "args": [],
      "env": {}
    }
  }
}

3. Restart Claude to load the MCP server

Available Tools

The MCP server provides the following tools:

connect_hfsql

Connect to an HFSQL database using an ODBC connection string.

{
  "name": "Connection Name",
  "connectionString": "DSN=MyHFSQLDatabase;UID=username;PWD=password"
}

disconnect_hfsql

Disconnect from a previously connected HFSQL database.

{
  "connectionId": "conn_1234567890"
}

list_tables

List all tables in a connected HFSQL database.

{
  "connectionId": "conn_1234567890"
}

describe_table

Get the structure of a table in a connected HFSQL database.

{
  "connectionId": "conn_1234567890",
  "tableName": "Customers"
}

query_table

Execute a SQL query on a connected HFSQL database.

{
  "connectionId": "conn_1234567890",
  "query": "SELECT * FROM Customers WHERE Country = 'France'",
  "limit": 100
}

migrate_to_n8n

Send query results to an n8n webhook for further processing. Supports both standard n8n installations and Railway deployments.

{
  "queryId": "query_1234567890",
  "n8nUrl": "https://n8n.example.com/webhook/123456",
  "n8nApiKey": "optional-api-key"
}

For Railway deployments, you can provide additional Railway-specific parameters:

{
  "queryId": "query_1234567890",
  "n8nUrl": "webhook-path",
  "railwayProject": "your-railway-project-id",
  "railwayToken": "your-railway-auth-token",
  "railwayService": "your-n8n-service-name"
}

When Railway parameters are provided, the MCP server will automatically construct the full Railway URL and add the necessary headers for authentication.

export_to_json

Export query results as JSON.

{
  "queryId": "query_1234567890"
}

Example Workflows

Standard Workflow

1. Connect to an HFSQL database
2. List available tables
3. Describe a table structure
4. Query data from the table
5. Migrate the data to n8n for further processing

Railway Workflow

1. Connect to an HFSQL database
2. Query data from tables
3. Migrate data to n8n running on Railway:

   {
     "queryId": "query_1234567890",
     "n8nUrl": "webhook/my-workflow",
     "railwayProject": "project_1234567890",
     "railwayToken": "railway_token_1234567890",
     "railwayService": "n8n-service"
   }

4. n8n processes the data and can trigger further automations

Railway Integration

This MCP server includes special support for n8n instances running on Railway. When using the migrate_to_n8n tool with Railway parameters:

1. The server automatically constructs the proper Railway URL format
2. Authentication headers are added to the request
3. Railway project and service information is included in the metadata

To find your Railway project ID and service name:

1. Log in to your Railway dashboard
2. Select your project
3. The project ID is in the URL: https://railway.app/project/[project-id]
4. The service name is displayed in the services list

To generate a Railway token:

1. Go to your Railway account settings
2. Navigate to the "Tokens" section
3. Create a new token with appropriate permissions

License

MIT