Devart MCP Server for PostgreSQL (ADO.NET)

com.devart由 devart.com 發布v1.1.0更新於 Oct 24, 2026

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

已驗證STDIO僅桌面資料庫資料與分析

概覽

AI 產生的概覽

讓 AI 用戶端透過 Devart dotConnect ADO.NET 或 ODBC 連線,以自然語言查詢與修改 PostgreSQL 資料庫。

可以做什麼
  • 把自然語言請求轉成結構化 SQL 查詢,並在已設定的 PostgreSQL 資料庫上執行
  • 檢視資料庫結構、說明資料表與關聯、探索 join,用於逆向分析或排錯
  • 為臨時分析與報表取數,包括訂單、訂閱、付款與帳戶歷程
  • 透過 stdio 或 HTTP 傳輸把整理好的結構化結果回傳給 AI 用戶端
適用情境
適合以 PostgreSQL 為主要資料來源的團隊:分析師、開發者、DBA 或客服人員想用自然語言提問而不寫 SQL,或需要讓資料留在自家環境、同時給 AI 工具一條受控的存取路徑。
執行需求
在 Windows 上以 .NET 8 建置版本或安裝程式本機執行;需要 Devart dotConnect for PostgreSQL 或 Devart ODBC Driver for PostgreSQL 連線,並在 mcpserver.json 中設定連線名稱、連線字串或 DSN 以及通訊協定類型。連線字串透過環境變數 DEVART_MCP_POSTGRESQL_CONNECTION 提供,連線字串中還需填入 Devart 授權金鑰。
安裝前請注意
連線字串含有資料庫憑證與授權金鑰,應把 DEVART_MCP_POSTGRESQL_CONNECTION 視為機密保管。伺服器提供讀寫存取,助理可能修改或刪除目標資料庫中的資料,建議使用最小權限帳號。所需的 Devart ODBC 驅動程式為付費產品,僅提供 30 天試用;HTTP 傳輸會在本機開啟監聽埠。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Devart MCP Server for PostgreSQL (ADO.NET),將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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

來源:README.md,提交 07a2e6e

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v1.1.0最新Sep 23, 2026

評分

已滿足適用檢查項的 40%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。