Connects to PostgreSQL as a read-only data source, extracting one CSV file per table into a shared folder that is then served over MCP for AI agents to read.
Connect your database to your AI agent, read-only, without sharing your password. Maplith Bridge serves a folder of data files over MCP behind a token you create, and fills it from PostgreSQL under a role that can only read.
6
2
171 npm
1
Apache 2.0
Why this server?
Allows using PostgreSQL with pgvector as a storage backend for memories, supporting persistent and shared memory across processes.
Agent memory for facts that change. When a user corrects something, Recall replaces the old fact, tells the agent what it replaced, and keeps the old value in a history. Ask what was believed on any date, see every change to a fact, or diff two dates. Runs locally on polign_db, Postgres with pgvector, MongoDB, or Qdrant. Apache 2.0.
14
5
13
Apache 2.0
Why this server?
Provides database operations for PostgreSQL, including querying, dumping, restoring, and maintenance.
Local-first operator MCP server: recall across your own sessions, chats and files, an
encrypted vault, SSH to your own hosts, and gated shell, browser and device tools.
130 tools over stdio or HTTP; everything runs on your machine — no hosted service,
no account, no API key.
28
15
523 PyPI
5
Apache 2.0
Why this server?
Runs a local PostgreSQL instance as part of a Flisk stack, automatically injects DATABASE_URL into services, and supports PostgreSQL-backed agent session checkpoint durability.
Let your AI build and run a whole app on your computer: an online shop, website, booking app or AI helper. It creates the parts, starts them, checks they work and fixes problems.
4
23
12,016 npm
36
MIT
Why this server?
Connects read-only to PostgreSQL instances (15–18, plus managed offerings) to run an evidence-based health-check rule catalog, producing an A–F graded report with findings, coverage and next actions. Also lists and describes tables and answers questions with a single read-only SELECT at a time, within row and time limits.
Read-only MCP server for SQL Server and PostgreSQL health checks. It runs the codeDB Lens diagnosis (A–F grade with rule coverage, findings with evidence, impact and next actions), reads 24-hour performance recordings, lists databases and tables, describes table schemas, and runs one guarded SELECT at a time within per-profile row and time limits. It uses the user's saved connection profiles; pass
6
14
7
Apache 2.0
Why this server?
Allows auditing PostgreSQL database performance, providing tools for analyzing table health, slow queries, index usage, and configuration.
Read-only PostgreSQL performance auditing via MCP. Collects metrics from PostgreSQL system views, applies deterministic checks for index, query, vacuum, configuration, and connection issues, and returns structured findings for MCP clients.
6
MIT
Why this server?
One of the SQL dialects targeted by the polyglot SQL transpiler, and supported by the schema migration differ, query plan optimizer, index advisor, and other SQL tools.
Enables AI agents to run deterministic database intelligence tasks including natural-language-to-SQL synthesis, AST SQL auditing and optimization, schema migration diffing, SQL transpilation, index and normalization advice, PII scrubbing, fixture generation, connection-pool sizing, isolation-hazard auditing, and ORM model compilation over Streamable HTTP or stdio.
1
12
MIT
Why this server?
Stores ZenBrain's memory in PostgreSQL, with pgvector support for embeddings, enabling self-hosted persistent memory across sessions.
Five-layer agent memory over MCP. zenbrain_store routes each memory: steps to a procedure, emotional weight to an episode, high confidence to a pinned core memory, the rest to a semantic fact. zenbrain_recall returns results with id and layer; zenbrain_forget deletes one plus what consolidation linked to it; zenbrain_consolidate runs one sleep-like pass. Local SQLite, no account, no network call.
5
28
Apache 2.0
Why this server?
Provides strictly read-only query access to PostgreSQL databases, allowing agents to run a single SELECT statement and retrieve paged or downloadable results in Parquet format.
Gives AI agents strictly read-only query access to PostgreSQL, Oracle, Cosmos DB, Blob Storage, Log Analytics, and Redis, returning each query as a paged or downloadable result set in Parquet or NDJSON rather than inline rows.
