PostgreSQL Docs MCP
Related Servers
Alternatives to PostgreSQL Docs MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables read-only access to generated technical documentation across one or multiple documented repositories, exposing tools to search code and docs, inspect modules and symbols, list gaps, review architecture, and check freshness with file#line citations.MIT
- FlicenseNot gradedqualityDmaintenanceEnables creating, listing, and searching project-based documentation with Markdown content, table of contents, full-text search, and multi-client support via Streamable HTTP transport.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search and ask questions across versioned service documentation, retrieve documents and diffs, and find related docs with cited answers over Streamable HTTP, SSE, or stdio.163 npmMIT
- FlicenseNot gradedqualityDmaintenanceIndexes public documentation sites into PostgreSQL and exposes retrieval-only MCP tools for listing sources, searching with citations, and fetching documents.5 npm-
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to access and read mdbook documentation, including structure, content, and search.4 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to search and read public Ravensight documentation over unauthenticated remote HTTP, retrieving cited excerpts and Markdown sections with revision-aware pagination. Provides a browsable index of document IDs and sections, with read-only, free access that cannot touch customer studios or player data.MIT
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.