Devart Mcp Server Xbase

Devart MCP Server for xBase

Devart MCP Server for xBase

Devart MCP Server for xBase enables AI clients to interact with your data through a secure server running in your environment. It turns a regular AI chat into a practical way to work with real-world business data — and it is faster than conventional export or manual querying.

Key benefits

Devart MCP Server for xBase allows you to:

• Work with data intuitively through natural language.
• Retrieve the required data for analysis within minutes.
• Generate reports faster with AI-powered assistance.
• Minimize manual data handling and integration maintenance.

How it works

Devart MCP Server for xBase helps AI clients communicate directly with xBase databases using natural-language prompts. It translates AI requests into structured queries, executes them through Devart connectivity drivers, and returns clean, structured results for seamless AI-powered data access.

Quick start

To get started with Devart MCP Server for xBase:

1. Download and install Devart ODBC Driver for xBase.

2. Download and install Devart MCP Server for xBase.

3. In Devart MCP Server for xBase, configure your data connection and integration settings.

4. Run your first natural-language query.

Need an MCP Server for multiple data sources?

Manual installation and configuration

Prerequisites

Before building and running Devart MCP Server for xBase, ensure the following components are installed:

• .NET 8 SDK
• ODBC connection — Devart.AI.McpServer.Odbc.xBase.csproj Devart ODBC Driver for xBase (requires manual download and installation)

Step 1: Clone the repository

Clone the project repository and navigate to the project directory:

1. Open Command Prompt.

2. Enter the following command:

git clone https://github.com/devart-ai-connectivity/devart-mcp-server-xbase.git
cd devart-mcp-server-xbase

Step 2: Build the MCP Server from source

You can build Devart MCP Server for xBase from source using ODBC.

To build the MCP server with ODBC, select the command based on the bitness of your data source.

• For 64-bit data source, run the following command:

dotnet publish Devart.AI.McpServer.Odbc/Devart.AI.McpServer.Odbc.xBase/Devart.AI.McpServer.Odbc.xBase.csproj -c ReleasexBase -r "win-x64" /p:TargetFramework=net8.0

• For 32-bit data source, run the following command:

dotnet publish Devart.AI.McpServer.Odbc/Devart.AI.McpServer.Odbc.xBase/Devart.AI.McpServer.Odbc.xBase.csproj -c ReleasexBase -r "win-x86" /p:TargetFramework=net8.0

Note

The target platform must match the bitness of your ODBC data source.

Step 3: Configure the database connection for the MCP Server

1. Create an mcpserver.json configuration file in the directory containing the built MCP Server executable.

2. In the file, configure the database connection:

{
  "Connections": [
    {
      "Name": "my_xbase",
      "DsnName": "your_dsn_name",
      "ProtocolType": "stdio"
    }
  ]
}

Alternatively, you can configure the database connection using the connection string:

{
  "Connections": [
    {
      "Name": "my_xbase",
      "ConnectionString": "Driver={Devart ODBC Driver for xBase};Server=localhost;User ID=xbase;Password=your_password;Database=your_database;",
      "ProtocolType": "stdio"
    }
  ]
}

where:

• Name — The name of the ODBC connection.

• DsnName — The name of your data source.

• ProtocolType — A transport protocol. The possible options are: stdio or http.

• HttpPort (required if ProtocolType is set to http) — The port number for the http protocol.

Step 4: Run the MCP server

After you configure the MCP Server, you can start it.

Note

This step is required only when ProtocolType is configured as http. If you use the stdio transport protocol, your AI client starts the server automatically.

To start the server, run the following command:

Devart.AI.McpServer.Odbc.xBase.exe run my_xbase

where my_xbase is the name of the ODBC connection.

Step 5: Integrate with Claude Desktop

1. Open claude_desktop_config.json, the Claude configuration file.

Tip

If you can't locate the configuration file, it may not exist yet. To create it, open Claude Desktop and navigate to File > Settings > Developer, then click Edit Config. The folder with the claude_desktop_config.json file opens.

2. Add one of the following objects, depending on the transport protocol used by MCP Server:

• STDIO

{
  "mcpServers": {
    "devart": {
      "command": "C:\\path\\to\\Devart.AI.McpServer.Odbc.xBase.exe",
      "args": [
        "run",
        "my_xbase"
      ]
    }
  }
}

where:

• devart is the connector name that will appear in Claude Desktop.

• C:\\path\\to\\Devart.AI.McpServer.Odbc.xBase.exe is the path to the executable file.

• my_xbase is the connection name specified in the mcpserver.json configuration file.

• HTTP

    "mcpServers": {
      "devart": {
        "command": "npx",
        "args": [
          "-y",
          "mcp-remote",
          "http://localhost:5000/sse"
        ]
      }
    }
  

  where:

  • devart is the connector name that will appear in Claude Desktop.
  • 5000 is the MCP Server listening port.

3. Save the file.

4. Restart Claude Desktop.

Devart MCP Server for xBase is now integrated with Claude, and devart appears in the Claude Desktop app in Customize > Connectors.

You can also integrate Devart MCP Server for xBase with other AI clients such as Cline, Codex, Cursor, Visual Studio Code, Windsurf, Zed.

Supported clients

Devart MCP Server for xBase supports integration with the following AI clients:

• Claude Desktop
• Visual Studio Code
• Cursor
• Codex
• Windsurf
• Cline
• Zed
• ...and other MCP-compatible AI clients

Typical use cases

Devart MCP Server for xBase is a practical fit for teams working with xBase as their primary data source.

• Legacy system data modernization
  Use AI to explore, document, and extract insights from DBF databases embedded in legacy dBASE, FoxPro, or Clipper applications still running in production.

• Retail and point-of-sale data access
  Query product catalogs, transaction histories, and inventory records stored in xBase format by older retail or POS systems.

• Government and public sector legacy data
  Access structured data from government systems that continue to use DBF-format databases as the underlying storage layer.

• Migration assessment and planning
  Analyze the structure, volume, and content of xBase databases to plan migration to a modern RDBMS with AI assistance in data mapping.

• Logistics and supply chain records
  Query shipment records, route data, and warehouse inventory stored in xBase databases used by legacy logistics and distribution systems.

• Historical business data retrieval
  Retrieve and analyze historical operational data from DBF archives that predate modern database platforms but still hold business-critical records.

Licensing and activation

Devart MCP Server for xBase is distributed as a free single-source MCP server.

To connect to xBase, the server requires the corresponding Devart ODBC Driver for xBase, which is a paid product.

A 30-day free trial is available for the Devart ODBC Driver for xBase.

See the product page and documentation for the latest installation and activation details.

Support

• Documentation
• Submit a request
• Suggest a feature
• Join our forum

Other Devart connectivity solutions

• MCP Server Universal
• ODBC Driver for xBase