Maplith Bridge
OfficialRelated Servers
Alternatives to Maplith Bridge
- AlicenseAqualityDmaintenancePostgres Pro is an open source Model Context Protocol (MCP) server built to support you and your AI agents throughout the entire development process—from initial coding, through testing and deployment, and to production tuning and maintenance.93,402MIT
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that gives an AI agent scoped, safe access to your Postgres databases with per-connection access control, row caps, timeouts, and defense-in-depth read-only enforcement.-
- AlicenseNot gradedqualityCmaintenanceA read-only PostgreSQL MCP server that enables AI agents to perform schema introspection and execute SELECT-only queries. It supports secure database connections through SSL and SSH tunnels while offering a structure-only mode to restrict query access.10 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides read-only access to PostgreSQL databases via MCP, enforcing least-privilege roles, row-level security, masked views, and SQL AST guardrails to prevent data leakage and unauthorized operations, enabling AI agents to safely query sensitive production data.MIT
- FlicenseNot gradedqualityDmaintenanceBridgeMCP turns SQLite databases or CSV folders into read-only MCP tools for Claude, with enforced security layers and full audit logging.-
- FlicenseBqualityBmaintenanceEnables Claude Desktop and custom AI agents to securely access enterprise Postgres databases and Notion knowledge bases via MCP, with read-only SQL enforcement, audit logging, and API-key authentication.1-
- AlicenseAqualityDmaintenanceA production-grade MCP server that gives AI agents safe, authenticated access to a PostgreSQL database.3MIT
TDQS
Scored across 2 tools
The two tools have distinct, non-overlapping purposes: list_files enumerates shared files with pagination, while read_file retrieves one file's contents by URI. There is no plausible way to misselect between them.
Both names follow a clean verb_noun snake_case pattern (list_files, read_file), with list/read being the natural verbs for a read-only file bridge.
Two tools is thin, but it matches the deliberately minimal read-only bridging scope. An agent has no way to search, filter, or check availability beyond a full listing, which is a real limitation of such a small surface.
For a read-only file-sharing bridge, list + read covers the core lifecycle and the descriptions even address pagination and the 8 MB truncation case. Minor gaps remain: no search/filter by name or mimeType, and no stat/metadata tool beyond what list_files returns.