This is a template project for those looking to build their own MCP servers. I designed it to be dead simple to understand and adapt - the code is
This is a template project for those looking to build their own MCP servers. I designed it to be dead simple to understand and adapt - the code is straightforward with MCP docs attached so you can quickly get up to speed. Exposed over MCP by the simple psql mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Model Context Protocol (MCP) is a standard way for LLMs to interact with external tools and data. In a nutshell:
Everything the assistant can do here goes through one of these:
execute_query — Run SQL queries against your databasetest_connection — Verify the database connection is workingYou will need one environment variable: SCHEMA. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
The server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Simple Psql MCP's toolset — execute_query, test_connection — is a fair guide to whether it matches your workflow. It is maintained by NetanelBollag; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| execute_query | Run SQL queries against your database |
| test_connection | Verify the database connection is working |
{
"mcpServers": {
"simple-psql": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"SCHEMA": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| SCHEMA | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.