What prerequisites are needed to run DBtoolReader?
Go 1.16 or higher, a PostgreSQL database, and access credentials for that database.
@JavaPanda30
Basic information
No overview available yet
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
DBtoolReader is a PostgreSQL database tool built with Go that provides a server interface for executing database queries and retrieving schema information. It integrates with the MCP (Model Context Protocol) server framework, making it usable with any LLM and LLM system.
After building the project with go build -o dbtoolreader, run it with ./dbtoolreader. The server communicates through standard input/output and responds to commands for executing database queries and retrieving schema information.
Go 1.16 or higher, a PostgreSQL database, and access credentials for that database.
It uses the `github.com/mark3labs/mcp-go` MCP server framework and other dependencies as listed in its `go.mod` file.
It uses a Stdio-based server interface, communicating through standard input and output, making it suitable for integration with other tools and services.
Two main tools: a Database Query Tool for executing queries against your PostgreSQL database, and a Schema Tool for retrieving schema information from the database.

Model Context Protocol Servers
Local MCP server for DuckDB and MotherDuck
Universal MCP-Server for your Databases optimized for LLMs and AI-Agents.
A MCP (model context protocol) server that gives the LLM access to and knowledge about relational databases like SQLite, Postgresql, MySQL & MariaDB, Oracle, and MS-SQL.
Drop-in Apache Spark replacement written in Rust, unifying batch processing, stream processing, and compute-intensive AI workloads.
Comments