MCP-PostgreSQL-Ops AI Integration

[Tool Purpose]: Monitor current locks and potential deadlocks in PostgreSQL [Exact Functionality]: - List all current locks held and waited for by sessions - Show blocked and blocking sessions, lock types, and wait status - Help diagnose lock contention and deadlock risk - Filter results by granted status, state, mode, lock type, or username [Required Use Cases]: - When user requests "lock monitoring", "deadlock check", "blocked sessions", etc. - When diagnosing performance issues due to locking - When checking for blocked or waiting queries - When filtering specific types of locks or users [Strictly Prohibited Use Cases]: - Requests for killing sessions or force-unlocking - Requests for lock configuration changes - Requests for historical lock data (only current state is shown) Args: database_name: Database name to analyze (uses default database if omitted) granted: Filter by granted status ("true" or "false") state: Filter by session state ("active", "idle", "idle in transaction", etc.) mode: Filter by lock mode ("AccessShareLock", "ExclusiveLock", etc.) locktype: Filter by lock type ("relation", "transactionid", "virtualxid", etc.) username: Filter by specific username Returns: Table-format information showing PID, user, database, lock type, relation, mode, granted, waiting, and blocked-by info

[Tool Purpose]: Monitor WAL (Write Ahead Log) status and statistics [Exact Functionality]: - Show current WAL location and LSN information - Display WAL file generation rate and size statistics - Monitor WAL archiving status and lag - Provide WAL-related configuration and activity metrics [Required Use Cases]: - When user requests "WAL status", "WAL monitoring", "log shipping status", etc. - When diagnosing replication lag or WAL archiving issues - When monitoring database write activity and WAL generation [Strictly Prohibited Use Cases]: - Requests for WAL configuration changes - Requests for manual WAL switching or archiving - Requests for WAL file manipulation or cleanup Returns: WAL status information including current LSN, WAL files, archiving status, and statistics

[Tool Purpose]: Monitor PostgreSQL replication status and statistics [Exact Functionality]: - Show current replication connections and their status - Display replication lag information for standbys - Monitor WAL sender and receiver processes - Provide replication slot information and statistics [Required Use Cases]: - When user requests "replication status", "standby lag", "replication monitoring", etc. - When diagnosing replication issues or performance problems - When checking replication slot usage and lag [Strictly Prohibited Use Cases]: - Requests for replication configuration changes - Requests for replication slot creation or deletion - Requests for failover or switchover operations Returns: Replication status including connections, lag information, slots, and statistics

[Tool Purpose]: Check basic information and connection status of PostgreSQL server [Exact Functionality]: - Retrieve PostgreSQL server version information - Display connection settings (with password masking) - Verify server accessibility - Check installation status of extensions (pg_stat_statements, pg_stat_monitor) [Required Use Cases]: - When user requests "server info", "PostgreSQL status", "connection check", etc. - When basic database server information is needed - When preliminary check is needed before using monitoring tools [Strictly Prohibited Use Cases]: - Requests for specific data or table information - Requests for performance statistics or monitoring data - Requests for configuration changes or administrative tasks Returns: Comprehensive information including server version, connection info, and extension status

[Tool Purpose]: Get information about the current database connection [Exact Functionality]: - Show the name of the currently connected database - Display database-specific information like encoding, locale, and size - Provide connection context for clarity in multi-database environments [Required Use Cases]: - When user asks "what database am I connected to?", "current database", etc. - When clarifying database context for analysis operations - When troubleshooting connection issues or confirming target database [Strictly Prohibited Use Cases]: - Requests for database structure changes or creation/deletion - Requests for user authentication or permission changes - Requests for configuration modifications Args: database_name: Target database to get info for (uses default connection if omitted) Returns: Current database name and related information for connection clarity