dbconvert-streams
Related Servers
Alternatives to dbconvert-streams
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables read-only SQL querying and exploration of data files (CSV, Parquet, JSON, Excel, etc.) via DuckDB, supporting local paths, globs, URLs, and S3 buckets.5MIT
- AlicenseAqualityCmaintenanceEnables AI agents to discover and query data federated across MySQL/MariaDB, PostgreSQL, ClickHouse, S3 and Kafka with SQL, exposing tools to list databases, schemas, tables and connections, describe columns, search objects, inspect table statistics, run EXPLAIN, and execute arbitrary statements. It runs locally over stdio against a PostgreSQL-wire endpoint and returns structured results or SQLSTATE-coded errors.8Apache 2.0
- AlicenseAqualityAmaintenanceRead-only, PII-masked MCP server for querying data federated through DuckDB — list sources/tables, inspect schemas, and run SQL across Postgres, MySQL, SQLite, Snowflake, BigQuery, Excel, and files, governed per source/table/column by a charter.yaml contract. Snowflake, BigQuery, Excel, and files, governed per source/table/column by a charter.yaml contract.649 PyPI15Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables read-only SQL queries across several named MySQL/MariaDB/Aurora and Postgres databases from one place, with tools to list databases, tables, and describe schemas. It enforces safety by requiring non-local hosts to be read replicas and by running every statement in a rolled-back read-only transaction.MIT
- FlicenseNot gradedqualityFmaintenanceProvides read-only SQL query access to Postgres and DuckDB databases via MCP tools, with extensive security hardening for public endpoints.1-
- AlicenseAqualityCmaintenanceQuery SQL databases (SQLite, PostgreSQL, BigQuery, Databricks) in natural language through a business semantic layer — glossary, metrics, and a data dictionary grounded against your real schema. Read-only by default, with an embedded SQLite + sqlite-vec metadata store and no external infra required.253MIT
TDQS
Scored across 2 tools
The two tools have complementary, non-overlapping roles: one lists connection summaries with basic metadata, and the other fetches detailed connection information. The descriptions explicitly cross-reference each other, so an agent should not confuse them.
Both tools follow the same dbconvert_<verb>_<noun> snake_case pattern (get_connection, list_data_sources), making the action and resource predictable and consistent.
Two tools is below the typical well-scoped range; while they cover a narrow read-only lookup use case cleanly, the surface feels thin for a product named DBConvert Streams and offers no operations beyond listing and inspecting connections.
The read-only connection metadata workflow (list then get detail) is covered, but the tool set omits connection lifecycle operations and any stream-related tools, so agents with broader management tasks will hit dead ends.