Devart MCP Server for MySQL (ADO.NET)

com.devartPublished by devart.comv1.1.0Updated Oct 24, 2026

Schema-aware read/write access to MySQL through Devart dotConnect ADO.NET data provider.

VerifiedSTDIODesktop onlyDatabasesData & Analytics

Overview

AI-generated overview

A local MCP server that gives AI assistants schema-aware read/write access to MySQL databases through Devart dotConnect ADO.NET or ODBC drivers.

What you can do
Translate natural-language requests into structured MySQL queries and execute them through Devart connectivity drivers, returning structured results for analysis and reporting. Explore MySQL schemas, trace table relationships, and help debug queries or understand legacy database structures. Query business data such as web analytics, e-commerce orders, inventory, CMS content, and subscription or revenue metrics without writing SQL. Read and write data, since the server provides schema-aware read/write access to the connected database.
When to use it
Useful when MySQL is your primary data source and you want an assistant to answer questions about real business data, produce reports, or help developers and DBAs explore schemas. It suits teams that want AI access kept within their own infrastructure rather than exporting data to external tools.
Requirements
Runs as a local process on the user's machine (desktop only). Requires .NET 8 SDK to build from source, a Devart dotConnect for MySQL ADO.NET provider or the Devart ODBC Driver for MySQL, and a configured connection in an mcpserver.json file. The connection string is supplied through the DEVART_MCP_MYSQL_CONNECTION environment variable. A Devart license key is needed for the paid driver.
Before you install
The server has read/write access to the connected MySQL database, so assistant-issued queries can change or delete data. The connection string, including database credentials and any license key, is a secret held in DEVART_MCP_MYSQL_CONNECTION and in the configuration file. The Devart ODBC Driver for MySQL is a paid product with only a 30-day trial, so continued use involves cost. Point it at a least-privilege database account and back up data before allowing write operations.

Installation

In SourceWeft

  1. Open Devart MCP Server for MySQL (ADO.NET) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Devart MCP Server for MySQL]

Version 1.1.0

What's new · Changelog

Devart MCP Server for MySQL

Devart MCP Server for MySQL 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 MySQL allows you to:

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

How it works

Devart MCP Server for MySQL helps AI clients communicate directly with MySQL 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.

[Devart MCP Server architecture]

Quick start

To get started with Devart MCP Server for MySQL:

1. Download and install Devart ODBC Driver for MySQL.

2. Download and install Devart MCP Server for MySQL.

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

[Devart MCP Server configuration]

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 MySQL, ensure the following components are installed:

  • .NET 8 SDK
  • ADO.NET connection — Devart.AI.McpServer.AdoNet.MySql.csproj Devart dotConnect for MySQL (installed automatically via NuGet during build)
  • ODBC connection — Devart.AI.McpServer.Odbc.MySql.csproj Devart ODBC Driver for MySQL (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:

cmd
git clone https://github.com/devart-ai-connectivity/devart-mcp-server-mysql.gitcd devart-mcp-server-mysql

Step 2: Build the MCP Server from source

You can build Devart MCP Server for MySQL from source using either of the supported database connectivity technologies: ADO.NET or ODBC.

  • To build the MCP server with ADO.NET, run the following command:
cmd
dotnet publish Devart.AI.McpServer.AdoNet/Devart.AI.McpServer.AdoNet.MySql/Devart.AI.McpServer.AdoNet.MySql.csproj -c ReleaseMySql /p:TargetFramework=net8.0

The Devart dotConnect for MySQL NuGet package is downloaded and restored automatically.

  • 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:

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

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

cmd
dotnet publish Devart.AI.McpServer.Odbc/Devart.AI.McpServer.Odbc.MySql/Devart.AI.McpServer.Odbc.MySql.csproj -c ReleaseMySql -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.

  • Configure a connection with ADO.NET.

Add the following configuration to the mcpserver.json file:

json
{  "Connections": [    {      "Name": "my_mysql",      "ConnectionString": "Server=localhost;Port=3306;User Id=your_user;Password=your_password;Database=your_database;License Key=your_license_key;",      "ProtocolType": "stdio"    }  ]}
  • Configure a connection with ODBC.

Add the following configuration to the mcpserver.json file:

json
{  "Connections": [    {      "Name": "my_mysql",      "DsnName": "your_dsn_name",      "ProtocolType": "stdio"    }  ]}
  • Configure a connection with ODBC using a connection string.

Add the following configuration to the mcpserver.json file:

json
{  "Connections": [    {      "Name": "my_mysql",      "ConnectionString": "Driver={Devart ODBC Driver for MySQL};Server=localhost;User ID=mysql;Password=your_password;Database=your_database;",      "ProtocolType": "stdio"    }  ]}

where:

  • Name — The connection name.

  • ConnectionString (applies to ADO.NET) — A database-specific connection string used to establish a connection to the target database.

  • DsnName (applies to ODBC) — 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 with ADO.NET, run the following command:
cmd
Devart.AI.McpServer.AdoNet.MySql.exe run my_mysql
  • To start the server with ODBC, run the following command:
cmd
Devart.AI.McpServer.Odbc.MySql.exe run my_mysql

where my_mysql 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
json
{  "mcpServers": {    "devart": {      "command": "C:\\path\\to\\Devart.AI.McpServer.AdoNet.MySql.exe",      "args": [        "run",        "my_mysql"      ]    }  }}

where:

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

  • C:\\path\\to\\Devart.AI.McpServer.AdoNet.MySql.exe is the path to the executable file. For an ODBC connection, use Devart.AI.McpServer.Odbc.MySql.exe.

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

  • HTTP

    json
      "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 MySQL is now integrated with Claude, and devart appears in the Claude Desktop app in Customize > Connectors.

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

Supported clients

Devart MCP Server for MySQL 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 MySQL is a practical fit for teams working with MySQL as their primary data source.

  • Web application analytics
    Query user behavior, session data, conversion funnels, and engagement metrics stored in MySQL-backed web apps without writing SQL.

  • E-commerce data exploration
    Analyze orders, products, inventory levels, customer records, and sales trends directly from MySQL databases powering WooCommerce, Magento, or custom storefronts.

  • CMS and content platform analysis
    Access and analyze content, taxonomies, user activity, and publishing history from WordPress, Drupal, or other MySQL-based content platforms.

  • Developer copilot for MySQL schemas
    Help developers and DBAs explore table structures, trace relationships, debug queries, and understand legacy schemas faster with AI assistance.

  • SaaS product and subscription reporting
    Let product and finance teams extract usage metrics, subscription states, churn signals, and revenue data directly from MySQL without BI tooling.

  • Secure on-premises AI access to MySQL
    Keep MySQL data entirely within your infrastructure while enabling AI tools to answer questions about real business data on demand.

Licensing and activation

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

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

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

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

Support

Other Devart connectivity solutions

Source: README.md at commit 5c468c3

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.0LatestSep 23, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.