PostgreSQL Docs MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_versionsA | List every PostgreSQL documentation version available online. Includes current supported releases, prereleases, the development snapshot, and archived unsupported releases. |
| search_docsA | Search the official PostgreSQL documentation within one version. Args: query: Search terms, such as "logical replication conflicts". version: "current", "devel", or a published version such as "18" or "9.6". limit: Number of results to return, from 1 to 20. |
| get_doc_pageA | Read one page from the official PostgreSQL documentation as Markdown. Use the page slug returned by search_docs. Long pages can be continued by calling this tool again with the next offset. Args: page: Page slug, such as "sql-select" or "functions-json.html". version: "current", "devel", or a published version such as "18" or "9.6". offset: Character offset at which to start reading. max_chars: Maximum characters to return, from 1,000 to 50,000. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: search_docs finds pages, get_doc_page reads a specific page, and list_versions enumerates available versions. There is no overlap, and the descriptions explicitly link them (get_doc_page uses slugs returned by search_docs).
All three names follow a consistent verb_noun snake_case pattern: search_docs, get_doc_page, list_versions. The convention is predictable and readable.
Three tools is exactly the right scope for a documentation search server: discover, retrieve, and enumerate versions. Each tool earns its place with no redundancy.
The surface covers the core lifecycle of finding and reading docs, including version selection and pagination via offset/max_chars. Minor gaps like no table-of-contents browsing or in-page search exist, but agents can work around them using search_docs.