Skip to main content
Glama
675,423 tools. Updated 2026-10-19 05:13

"Connecting to PostgreSQL database, retrieving table schema, and executing SQL queries" matching MCP tools:

  • Retrieve the archive database schema, including table and column names. Understand available data for crafting SQL queries.
    Apache 2.0
  • Run SQL queries to analyze, modify, or troubleshoot Heroku PostgreSQL databases. Execute commands or file-based queries with credential management for direct database access.
    Apache 2.0
  • Validate SQL query syntax without executing it. Uses an EXPLAIN-like check to confirm the query is valid for the target database. Works with engines like PostgreSQL.
    MIT
  • Execute SQL queries via Superset's SQL Lab to retrieve data. Provide database ID and SQL; set schema, catalog, or template params as needed.
    MIT
  • Switches the active PostgreSQL server and database connection. Required before executing queries; specify server from list_servers and optionally select database and schema.
    MIT

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI assistants to query PostgreSQL, MySQL, SQL Server, Oracle, and MongoDB databases through MCP with read-only, audited access.
    2
    AGPL 3.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    MCP server that connects to SQL databases (SQLite, PostgreSQL, MSSQL, MySQL) and provides tools to run read-only queries, list schemas/tables, and manage connections via stdio transport.
    Apache 2.0

Matching MCP Connectors

  • Execute a read-only SQL query against a stand's PostgreSQL database by providing the stand name and schema-qualified query.
    MIT
  • Execute SQL SELECT queries to retrieve data from Snowflake databases using fully qualified table names, including database, schema, and table details for accurate results.
    MIT
  • Execute parameterized SQL statements on a PostgreSQL database, returning rows and row counts.
    MIT
  • Analyzes SQL queries, table schemas, migrations, and index performance to identify issues and optimize database behavior.
    -
  • Run SQL queries on DuckDB or MotherDuck databases. Unqualified table names resolve automatically to the current database and schema.
    MIT
    Destructive
  • Describe database table columns, primary key, foreign keys, and indexes by querying the live catalog. Use before writing SQL joins or dashboard queries to verify column names and types.
    MIT
  • Generate SQL migration scripts by comparing database schemas. Compare live databases or a database against target DDL to create ALTER statements for schema updates.
    MIT
  • Lists every catalog, schema, and table you are allowed to query; call it first to ground table discovery and SQL writing.
    Apache 2.0
  • Retrieve counts, labels, edge types, and schema of your graph database to understand its state before writing queries or after mutations.
    Apache 2.0