Devart MCP Server for PostgreSQL (ADO.NET)

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

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

VerifiedSTDIODesktop onlyDatabasesData & Analytics

Overview

AI-generated overview

Lets an AI client query and modify PostgreSQL databases in natural language through Devart dotConnect ADO.NET or ODBC connectivity.

What you can do
  • Translate natural-language requests into structured SQL queries and execute them against a configured PostgreSQL database
  • Inspect schemas, explain tables and relationships, and explore joins for reverse engineering or troubleshooting
  • Retrieve data for ad-hoc analysis and reporting, including orders, subscriptions, payments and account history
  • Return clean, structured results to the AI client over stdio or HTTP transport
When to use it
Useful when PostgreSQL is the team's primary data source and analysts, developers, DBAs or support staff want to ask questions in natural language instead of writing SQL, or when data must stay on-premises while AI tools get a controlled path to it.
Requirements
Runs locally on Windows as a .NET 8 build (or the packaged installer); needs a Devart dotConnect for PostgreSQL or Devart ODBC Driver for PostgreSQL connection, configured in an mcpserver.json file with a connection name, connection string or DSN, and protocol type. The connection string is supplied through the DEVART_MCP_POSTGRESQL_CONNECTION environment variable. A Devart license key is entered in the connection string.
Before you install
The connection string holds database credentials and a license key, so treat DEVART_MCP_POSTGRESQL_CONNECTION as a secret. The server offers read/write access, so the assistant can change or delete data in the target database; point it at a least-privileged account. The required Devart ODBC Driver is a paid product with only a 30-day trial, and the HTTP transport exposes a local listening port.

Installation

In SourceWeft

  1. Open Devart MCP Server for PostgreSQL (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 PostgreSQL]

Version 1.1.0

What's new · Changelog

Devart MCP Server for PostgreSQL

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

1. Download and install Devart ODBC Driver for PostgreSQL.

2. Download and install Devart MCP Server for PostgreSQL.

3. In Devart MCP Server for PostgreSQL, 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 PostgreSQL, ensure the following components are installed:

  • .NET 8 SDK
  • ADO.NET connection — Devart.AI.McpServer.AdoNet.PostgreSql.csproj Devart dotConnect for PostgreSQL (installed automatically via NuGet during build)
  • ODBC connection — Devart.AI.McpServer.Odbc.PostgreSql.csproj Devart ODBC Driver for PostgreSQL (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-postgresql.gitcd devart-mcp-server-postgresql

Step 2: Build the MCP Server from source

You can build Devart MCP Server for PostgreSQL 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.PostgreSql/Devart.AI.McpServer.AdoNet.PostgreSql.csproj -c ReleasePostgreSql /p:TargetFramework=net8.0

The Devart dotConnect for PostgreSQL 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.PostgreSql/Devart.AI.McpServer.Odbc.PostgreSql.csproj -c ReleasePostgreSql -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.PostgreSql/Devart.AI.McpServer.Odbc.PostgreSql.csproj -c ReleasePostgreSql -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_postgresql",      "ConnectionString": "Server=localhost;Port=5432;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_postgresql",      "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_postgresql",      "ConnectionString": "Driver={Devart ODBC Driver for PostgreSQL};Server=localhost;User ID=postgres;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.PostgreSql.exe run my_postgresql
  • To start the server with ODBC, run the following command:
cmd
Devart.AI.McpServer.Odbc.PostgreSql.exe run my_postgresql

where my_postgresql 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.PostgreSql.exe",      "args": [        "run",        "my_postgresql"      ]    }  }}

where:

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

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

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

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

Supported clients

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

  • Self-service analytics on PostgreSQL data
    Let analysts, product managers, sales, finance, and operations teams ask natural-language questions without writing SQL.

  • Developer copilot for production PostgreSQL databases
    Help developers and DBAs investigate real data, inspect schemas, explore joins, and troubleshoot anomalies faster.

  • Support and customer operations investigation
    Let support teams quickly check orders, subscriptions, payments, statuses, and account history stored in PostgreSQL.

  • Schema exploration and reverse engineering
    Use AI to explain tables, relationships, and business logic in legacy or poorly documented PostgreSQL databases.

  • Ad-hoc reporting and internal analysis
    Generate one-off reports, investigate trends, and answer business questions directly from PostgreSQL without building a dashboard first.

  • Secure on-premises AI access to PostgreSQL
    Keep PostgreSQL data inside your infrastructure while giving AI tools a controlled path to work with real business data.

Licensing and activation

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

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

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

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

Support

Other Devart connectivity solutions

Source: README.md at commit 07a2e6e

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.