How do I install Devart MCP Server For SQL Server (ADO.NET)?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Devart MCP Server For SQL Server (ADO.NET) need an API key?

The publisher lists these environment variables: DEVART_MCP_SQLSERVER_CONNECTION.

What transport does Devart MCP Server For SQL Server (ADO.NET) use?

Devart MCP Server For SQL Server (ADO.NET) runs locally over stdio.

When was Devart MCP Server For SQL Server (ADO.NET) last checked?

Last checked 2026-11-08. Schema-aware read/write access to SQL Server through Devart dotConnect ADO.NET data provider.

Devart MCP Server For SQL Server (ADO.NET) MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

nuget Devart.Mcp.SqlServer

Credentials from the publisher

DEVART_MCP_SQLSERVER_CONNECTION — A dotConnect for SQL Server connection string.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1DEVART_MCP_SQLSERVER_CONNECTION=<secret> claude mcp add com.devart-mcp-sqlserver -- nuget Devart.Mcp.SqlServer

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "com.devart-mcp-sqlserver": {4      "command": "nuget",5      "args": [6        "Devart.Mcp.SqlServer"7      ],8      "env": {9        "DEVART_MCP_SQLSERVER_CONNECTION": "<secret>"10      }11    }12  }13}

claude_desktop_config.json

Local · nugetPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 1.1.0
API key

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

Version 1.1.0

What's new · Changelog

Devart MCP Server for SQL Server

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

1. Download and install Devart ODBC Driver for SQL Server.

2. Download and install Devart MCP Server for SQL Server.

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

Devart MCP Server configuration

4. Run your first natural-language query.

Manual installation and configuration

Prerequisites

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

.NET 8 SDK
ADO.NET connection — Devart.AI.McpServer.AdoNet.SqlServer.csproj Devart dotConnect for SQL Server (installed automatically via NuGet during build)
ODBC connection — Devart.AI.McpServer.Odbc.SqlServer.csproj Devart ODBC Driver for SQL Server (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-sqlserver.git
cd devart-mcp-server-sqlserver

Step 2: Build the MCP Server from source

You can build Devart MCP Server for SQL Server 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:

dotnet publish Devart.AI.McpServer.AdoNet/Devart.AI.McpServer.AdoNet.SqlServer/Devart.AI.McpServer.AdoNet.SqlServer.csproj -c ReleaseSqlServer /p:TargetFramework=net8.0

The Devart dotConnect for SQL Server 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:

dotnet publish Devart.AI.McpServer.Odbc/Devart.AI.McpServer.Odbc.SqlServer/Devart.AI.McpServer.Odbc.SqlServer.csproj -c ReleaseSqlServer -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.SqlServer/Devart.AI.McpServer.Odbc.SqlServer.csproj -c ReleaseSqlServer -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:

{
  "Connections": [
    {
      "Name": "my_sqlserver",
      "ConnectionString": "Server=localhost;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:

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

Configure a connection with ODBC using a connection string.

Add the following configuration to the mcpserver.json file:

{
  "Connections": [
    {
      "Name": "my_sqlserver",
      "ConnectionString": "Driver={Devart ODBC Driver for SQL Server};Server=localhost;User ID=sqlserver;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:

Devart.AI.McpServer.AdoNet.SqlServer.exe run my_sqlserver

To start the server with ODBC, run the following command:

Devart.AI.McpServer.Odbc.SqlServer.exe run my_sqlserver

where my_sqlserver 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.AdoNet.SqlServer.exe",
      "args": [
        "run",
        "my_sqlserver"
      ]
    }
  }
}

where:

devart is the connector name that will appear in Claude Desktop.
C:\\path\\to\\Devart.AI.McpServer.AdoNet.SqlServer.exe is the path to the executable file. For an ODBC connection, use Devart.AI.McpServer.Odbc.SqlServer.exe.
my_sqlserver 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 SQL Server is now integrated with Claude, and devart appears in the Claude Desktop app in Customize > Connectors.

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

Supported clients

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

.NET application data access
Query business data from SQL Server databases backing .NET web applications, APIs, and enterprise software, without SQL or developer involvement.
Microsoft Dynamics and ERP analytics
Access CRM, ERP, and operational data stored in SQL Server by Microsoft Dynamics on-premises deployments directly through AI tools.
SharePoint and intranet data exploration
Query content databases, list data, and metadata from SQL Server instances backing SharePoint or other Microsoft intranet platforms.
BI and reporting without SSRS
Answer ad-hoc business questions directly from SQL Server databases without building SSRS reports or waiting for BI team involvement.
Developer and DBA productivity
Help SQL Server developers and DBAs investigate data issues, explore stored procedures, audit schemas, and troubleshoot performance problems with AI assistance.
Secure on-premises AI access to SQL Server
Keep SQL Server data inside your infrastructure, including Azure-connected instances with private networking, while enabling AI-driven analysis.

Licensing and activation

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

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

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

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

Devart MCP Server For SQL Server (ADO.NET)

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Devart MCP Server For SQL Server (ADO.NET)?

Does Devart MCP Server For SQL Server (ADO.NET) need an API key?

What transport does Devart MCP Server For SQL Server (ADO.NET) use?

When was Devart MCP Server For SQL Server (ADO.NET) last checked?

Documentation

Version 1.1.0

Devart MCP Server for SQL Server

Key benefits

How it works

Quick start

Manual installation and configuration

Supported clients

Typical use cases

Licensing and activation

Support

Other Devart connectivity solutions