Devart MCP Server for PostgreSQL — MCP server for Postgres
An MCP server that lets an AI client read from and write to PostgreSQL on request in plain language. Runs on Devart drivers inside your environment.
Open on GitHubWhat Devart MCP Server for PostgreSQL (ADO.NET) does
The server sits between your AI client and the database. A prompt goes out, the server turns it into SQL, executes it through a Devart driver, and hands back structured rows. It reads the schema as well, so prompts can name real tables and columns.
You can build it two ways. The ADO.NET project needs the .NET 8 SDK; the Devart dotConnect for PostgreSQL package is pulled from NuGet during the build. The ODBC route means installing Devart ODBC Driver for PostgreSQL yourself, and the published binary must match the bitness of your data source. Connections live in mcpserver.json next to the built executable: a connection name plus either a connection string or a DSN.
With ADO.NET, the connection string carries a License Key field. Leave it out and the connection will not come up. stdio lets the client launch the server; http needs a manual start and an HttpPort value, so skip the run step entirely if you stay on stdio.
What it helps with
- inspect tables in PostgreSQL without writing SQL by hand
- pull a summary of business data into the chat
- check the schema before editing a migration
- insert rows by describing the change in words
Example prompts for the agent
- List the latest rows in
ordersand count the cancelled ones - Compare order counts for March and April in
orders - Add a
stdioconnection namedmy_postgresqltomcpserver.json
How to install Devart MCP Server for PostgreSQL (ADO.NET)
Install
The MCP registry has no launch command for it: see the repository README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Devart MCP Server for PostgreSQL (ADO.NET)
How do I install Devart MCP Server for PostgreSQL?
There is no single package: download and install Devart ODBC Driver for PostgreSQL from Devart, then the MCP server itself, then open it and set up the data connection and integration options. Building from source is the other route: git clone https://github.com/devart-ai-connectivity/devart-mcp-server-postgresql.git, then `dotnet publish Devart.AI.McpServer.AdoNet/Devart.AI.McpServer.AdoNet.PostgreSql/Devart.AI.McpServer.AdoNet.PostgreSql.csproj -c ReleasePostgreSql /p:TargetFramework=net8.0`.
What does Devart MCP Server for PostgreSQL do?
It takes natural-language requests from an AI client and runs them against PostgreSQL through a Devart driver. Results come back structured, ready to use in the conversation.
How does the ADO.NET build differ from the ODBC one?
ADO.NET requires the .NET 8 SDK and restores dotConnect from NuGet at build time. ODBC requires the Devart driver installed by hand, and the build must target win-x64 or win-x86 to match your data source.
