MCP server de Devart SQL
Commit 3 sept 2026Permite que los clientes de IA interactúen con bases de datos SQL Server mediante lenguaje natural utilizando conectividad ADO.NET u ODBC.
También conocido como devart-ai-connectivity/devart-mcp-server-sqlserver, devart-mcp-server-sqlserver
- Stars
- 0
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- 1.1.0
- Último commit
- 3 sept 2026
- Licencia
- —
¿Qué es Devart SQL MCP?
Permite que los clientes de IA interactúen con bases de datos SQL Server mediante lenguaje natural utilizando conectividad ADO.NET u ODBC.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Devart SQL
Devart MCP Server for SQL Server permite que los clientes de IA interactúen con bases de datos SQL Server usando lenguaje natural. Funciona traduciendo los prompts del usuario en consultas estructuradas, que luego se ejecutan a través de los controladores de conectividad de Devart. Este servidor se ejecuta localmente en tu entorno, garantizando que los datos permanezcan dentro de tu infraestructura, incluyendo instancias conectadas a Azure con redes privadas.
Los desarrolladores pueden elegir entre conectividad ADO.NET u ODBC. Al compilar con ADO.NET se utiliza el paquete NuGet Devart dotConnect for SQL Server, mientras que la opción ODBC requiere el Devart ODBC Driver for SQL Server. El servidor admite protocolos de transporte como stdio, donde el cliente de IA inicia el servidor automáticamente, o http, que requiere un inicio manual en un puerto específico. Es compatible con varios clientes de IA, incluidos Claude Desktop, Cursor, Visual Studio Code, Windsurf y Zed.
La configuración implica configurar un archivo mcpserver.json con cadenas de conexión, nombres de DSN o claves de licencia. Aunque el MCP server es un proyecto de código único gratuito, la conexión a la base de datos requiere un proveedor ADO.NET o el Devart ODBC Driver de pago.
Qué puedes hacer con él
- 1Informes de negocio ad-hocHaz preguntas sobre datos de negocio directamente desde la base de datos sin necesidad de crear informes formales de SSRS.
- 2Asistencia en administración de bases de datosUtiliza la IA para ayudar a investigar problemas de datos, explorar procedimientos almacenados o solucionar problemas de rendimiento.
- 3Exploración de datos empresarialesAccede a datos operativos de Microsoft Dynamics o sistemas ERP almacenados en SQL Server a través de herramientas de IA.
- 4Acceso a datos para perfiles no técnicosConsulta datos de bases de datos que soportan aplicaciones .NET sin necesidad de conocimientos de SQL o ayuda de un desarrollador.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Configuración
DEVART_MCP_SQLSERVER_CONNECTIONObligatorioSecretoA dotConnect for SQL Server connection string.
| Nombre | Descripción | Tipo |
|---|---|---|
| DEVART_MCP_SQLSERVER_CONNECTION | A dotConnect for SQL Server connection string. | ObligatorioSecreto |
Verificaciones automáticas
Ejecutado 15 nov 2026Informe completo →Aún no verificado. Un servidor necesita una puntuación de 80, ningún hallazgo grave y suficientes datos para que podamos revisarlo. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesibledevart-ai-connectivity/devart-mcp-server-sqlserver is public and reachablegithub.com/devart-ai-connectivity/devart-mcp-server-sqlserve ↗Aprobado
- El paquete indica este repositorio como su origenNo verificado
- Procedencia de la compilación (atestación de Sigstore)No verificado
- Licencia de código abierto (OSI)No licenseHallazgo
- Commit o lanzamiento en el último añoLast commit or release 2026-09-17github.com/devart-ai-connectivity/devart-mcp-server-sqlserve ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo verificado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPNo verificado
README
Ver en GitHubVersion 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
Preguntas sobre Devart SQL MCP
¿Cuáles son los requisitos previos para compilar el servidor desde el código fuente?
Necesitas el .NET 8 SDK y ya sea Devart dotConnect for SQL Server (para ADO.NET) o el Devart ODBC Driver for SQL Server.
¿Es gratuito el Devart MCP Server for SQL Server?
El MCP server en sí se distribuye como un servidor de código único gratuito, pero para conectarse a SQL Server se requiere un proveedor ADO.NET o el Devart ODBC Driver de pago.
¿Qué clientes de IA son compatibles?
Es compatible con Claude Desktop, Visual Studio Code, Cursor, Codex, Windsurf, Cline, Zed y otros clientes compatibles con MCP.

