Devart SQL MCP server
Commit 3. Sept. 2026Ermöglicht es AI-Clients, über ADO.NET oder ODBC-Verbindungen mittels natürlicher Sprache mit SQL Server Datenbanken zu interagieren.
Auch bekannt als devart-ai-connectivity/devart-mcp-server-sqlserver, devart-mcp-server-sqlserver
- Stars
- 0
- Tools
- —
- Downloads, 30 Tage
- —
- Neueste Version
- 1.1.0
- Letzter Commit
- 3. Sept. 2026
- Lizenz
- —
Was ist Devart SQL MCP?
Ermöglicht es AI-Clients, über ADO.NET oder ODBC-Verbindungen mittels natürlicher Sprache mit SQL Server Datenbanken zu interagieren.
Zusammenfassung generiert aus dem README des Projekts
Über Devart SQL MCP server
Der Devart MCP Server for SQL Server erlaubt es AI-Clients, über natürliche Sprache mit SQL Server Datenbanken zu interagieren. Er funktioniert, indem er User-Prompts in strukturierte Queries übersetzt, die dann über Devart Connectivity-Treiber ausgeführt werden. Dieser Server läuft lokal in deiner Umgebung, sodass deine Daten innerhalb deiner Infrastruktur bleiben, einschließlich Azure-verbundener Instanzen mit Private Networking.
Entwickler können zwischen ADO.NET oder ODBC-Connectivity wählen. Bei der Nutzung von ADO.NET wird das Devart dotConnect for SQL Server NuGet-Paket verwendet, während die ODBC-Option den Devart ODBC Driver for SQL Server erfordert. Der Server unterstützt Transportprotokolle wie stdio, wobei der AI-Client den Server automatisch startet, oder http, was einen manuellen Start auf einem spezifischen Port erfordert. Er ist kompatibel mit verschiedenen AI-Clients wie Claude Desktop, Cursor, Visual Studio Code, Windsurf und Zed.
Das Setup umfasst die Konfiguration einer mcpserver.json Datei mit Connection Strings, DSN-Namen oder Lizenzschlüsseln. Während der MCP server selbst ein kostenloses Single-Source-Projekt ist, erfordert die Verbindung zur Datenbank einen kostenpflichtigen Devart ODBC Driver oder einen ADO.NET Provider.
Was du damit machen kannst
- 1Ad-hoc Business-ReportingStelle Fragen zu Geschäftsdaten direkt aus der Datenbank, ohne formale SSRS-Reports erstellen zu müssen.
- 2Unterstützung bei der DatenbankadministrationNutze KI, um Datenprobleme zu untersuchen, Stored Procedures zu explorieren oder Performance-Probleme zu troubleshooten.
- 3Enterprise Data ExplorationGreife über AI-Tools auf operative Daten aus Microsoft Dynamics oder ERP-Systemen zu, die in SQL Server gespeichert sind.
- 4Datenzugriff für Nicht-TechnikerFrage Daten aus Datenbanken ab, die .NET-Anwendungen unterstützen, ohne SQL-Kenntnisse oder Hilfe von Entwicklern zu benötigen.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
Konfiguration
DEVART_MCP_SQLSERVER_CONNECTIONErforderlichSecretA dotConnect for SQL Server connection string.
| Name | Beschreibung | Typ |
|---|---|---|
| DEVART_MCP_SQLSERVER_CONNECTION | A dotConnect for SQL Server connection string. | ErforderlichSecret |
Automatisierte Checks
Geluften am 15. Nov. 2026Vollständiger Bericht →Noch nicht verifiziert. Ein Server benötigt einen Score von 80, keine kritischen Befunde und genug Daten für unsere Prüfung. Wie die Checks funktionieren · Was du für mehr Punkte verbessern kannst
- Source Repository verknüpft und erreichbardevart-ai-connectivity/devart-mcp-server-sqlserver is public and reachablegithub.com/devart-ai-connectivity/devart-mcp-server-sqlserve ↗Bestanden
- Paket nennt dieses Repository als QuelleNicht geprüft
- Build-Provenienz (Sigstore-Attestierung)Nicht geprüft
- Open Source Lizenz (OSI)No licenseBefund
- Commit oder Release im letzten JahrLast commit or release 2026-09-17github.com/devart-ai-connectivity/devart-mcp-server-sqlserve ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNicht geprüft
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenNicht geprüft
- Keine versteckten Anweisungen an das Modell0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-HandshakeNicht geprüft
README
Auf GitHub ansehenVersion 1.1.0
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.

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.

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:stdioorhttp. -
HttpPort(required ifProtocolTypeis set tohttp) — The port number for thehttpprotocol.
Step 4: Run the MCP server
After you configure the MCP Server, you can start it.
Note
This step is required only when
ProtocolTypeis configured ashttp. If you use thestdiotransport 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.jsonfile 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:
-
devartis the connector name that will appear in Claude Desktop. -
C:\\path\\to\\Devart.AI.McpServer.AdoNet.SqlServer.exeis the path to the executable file. For an ODBC connection, useDevart.AI.McpServer.Odbc.SqlServer.exe. -
my_sqlserveris the connection name specified in themcpserver.jsonconfiguration file. -
HTTP
"mcpServers": { "devart": { "command": "npx", "args": [ "-y", "mcp-remote", "http://localhost:5000/sse" ] } }where:
devartis the connector name that will appear in Claude Desktop.5000is 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.
Support
Other Devart connectivity solutions
Devart SQL MCP Fragen
Was sind die Voraussetzungen, um den Server aus dem Quellcode zu bauen?
Du benötigst das .NET 8 SDK und entweder Devart dotConnect for SQL Server (für ADO.NET) oder den Devart ODBC Driver for SQL Server.
Ist der Devart MCP Server for SQL Server kostenlos?
Der MCP server selbst wird als kostenloser Single-Source-Server bereitgestellt, aber die Verbindung zum SQL Server erfordert einen kostenpflichtigen Devart ODBC Driver oder einen ADO.NET Provider.
Welche AI-Clients werden unterstützt?
Er unterstützt Claude Desktop, Visual Studio Code, Cursor, Codex, Windsurf, Cline, Zed und andere MCP-kompatible Clients.

