Heroku MCP serverofficial
A
securityA
licenseA
qualityLet's your agent access the heroku platform
Last updated -
33
2,854
55
TypeScript
Apache 2.0
PostgreSQL is an advanced open source relational database management system that offers robustness, scalability, and performance.
Why this server?
Enables direct interaction with Heroku PostgreSQL databases, including executing SQL queries, viewing database information, managing active queries, identifying resource-intensive operations, handling credentials, managing backups, and performing database upgrades.
Why this server?
Enables integration with PostgreSQL databases for storing and querying Bitcoin Stamps metadata and collection statistics.
Why this server?
Enables interaction with Aiven for PostgreSQL services, allowing access to database resources hosted on the Aiven platform.
Why this server?
Implements an audit database for tracking changes made through the OPNSense MCP server
Why this server?
Enables confirmation workflows when working with PostgreSQL databases, particularly in verification steps for database implementations.
Why this server?
Enables access to PostgreSQL service configuration options in NixOS, allowing AI assistants to search and retrieve information about PostgreSQL service settings.
Why this server?
Provides tools for executing PostgreSQL queries against Supabase databases with risk assessment, parsing, and validation. Includes automatic migration versioning for database-altering operations.
Why this server?
Helps maintain database structure consistency when working with PostgreSQL schemas in your project
Why this server?
Connects to PostgreSQL databases to execute SQL queries and extract analytical insights
Why this server?
Enables real-time retrieval of table structure information from PostgreSQL databases, supporting both low-code system schema queries and traditional database metadata queries
Why this server?
Provides parameter conversion from PostgreSQL-style ($1) to Oracle-style (:1) for compatibility with PostgreSQL query formats.
Why this server?
Connects to CockroachDB using the PostgreSQL interface to provide database operations, table management, and query execution capabilities.
Why this server?
Connects to CockroachDB using PostgreSQL-compatible connection strings and protocols.
Why this server?
Planned future support for checking PostgreSQL database health and connectivity status
Why this server?
Supports PostgreSQL as a database technology option, allowing it to be specified during project creation and maintained in the project context
Why this server?
Supports database schema generation and API integration with PostgreSQL
Why this server?
Supports PostgreSQL database integration for persistent storage of workflow data
Why this server?
Provides comprehensive database management capabilities including connection profile setup, executing SQL queries, listing tables, describing table structures, and performing CRUD operations on data with built-in protection against SQL injection.
Why this server?
Provides comprehensive PostgreSQL database management capabilities, including database analysis, schema management, data migration, and real-time monitoring. Enables analyzing configurations, debugging issues, creating and altering tables, exporting/importing data between databases, and monitoring performance metrics.
Why this server?
Provides database integration for PostgreSQL in generated applications
Why this server?
Provides search across PostgreSQL documentation for database management and SQL queries
Why this server?
Provides tools for accessing and querying PostgreSQL databases through the AgentMode server
Why this server?
Connects to PostgreSQL databases, allowing for schema exploration, table descriptions, and SQL query execution.
Why this server?
Connects to PostgreSQL databases through Steampipe, enabling SQL-based queries across cloud infrastructure data
Why this server?
Provides tools for database health monitoring, index tuning, schema intelligence, query optimization, and protected SQL execution in PostgreSQL databases. Includes workload analysis, index recommendations, slow query identification, and database health checks.
Why this server?
Provides current documentation and code examples for PostgreSQL operations, helping users write accurate database scripts for tasks like conditional row deletion.
Why this server?
Provides PostgreSQL database management capabilities including analysis, setup instructions, and debugging for PostgreSQL database instances
Why this server?
Provides PostgreSQL database management capabilities, including analyzing existing PostgreSQL setups, implementation guidance, debugging database issues, managing schemas, migrating data, and monitoring database performance.
Why this server?
Allows AI agents to interact with multiple PostgreSQL databases, including running read-only queries, executing data-modifying statements, performing transactions, listing tables, and inspecting database schemas.
Why this server?
Connects to a PostgreSQL database, providing tools for schema exploration, read-only SQL query execution, relationship visualization, and data analysis through predefined templates and sample data retrieval.
Why this server?
Enables interaction with PostgreSQL databases, providing tools for executing queries, managing database connections, listing tables, and describing table structures with support for prepared statements and comprehensive error handling.
Why this server?
Allows importing data from CSV and Excel files into PostgreSQL databases
Why this server?
Allows connecting to and interacting with PostgreSQL databases, including listing tables, viewing triggers, listing functions, executing SQL queries, and exporting schema and data.
Why this server?
Supports SQL output format with PostgreSQL dialect for random user data, including CREATE TABLE statements and proper type handling.
Why this server?
Uses PostgreSQL for secure storage of healthcare data in the Clinical Data Repository
Why this server?
Listed as a supported data source for integration through the CData JDBC Driver framework.
Why this server?
Allows native SQL access to PostgreSQL relational databases.
Why this server?
Allows read-only access to PostgreSQL database data via SQL models.
Why this server?
Allows querying of PostgreSQL databases through relational SQL models.
Why this server?
Allows SQL querying of PostgreSQL database systems and data
Why this server?
Enables direct SQL querying of PostgreSQL database tables and data
Why this server?
Enables querying PostgreSQL data sources by exposing them as relational SQL models that can be accessed through natural language queries.
Why this server?
Allows direct SQL querying of PostgreSQL databases, providing full access to relational database tables and data.
Why this server?
Provides SQL-based access to PostgreSQL databases, enabling queries against PostgreSQL tables and data.
Why this server?
Enables direct SQL querying of PostgreSQL databases for advanced relational data access and database management operations.
Why this server?
Provides direct querying capabilities for PostgreSQL databases through SQL operations for relational database management and analysis.
Why this server?
Provides SQL access to PostgreSQL databases, exposing tables and views.
Why this server?
Provides access to PostgreSQL database tables and data through SQL queries
Why this server?
Provides direct access to PostgreSQL database tables and data through SQL operations
Why this server?
Listed as a supported data source that can be accessed through the CData JDBC driver integration.
Why this server?
Allows direct SQL querying of PostgreSQL database systems and their relational data structures.
Why this server?
Provides direct SQL access to PostgreSQL database tables and data
Why this server?
Enables direct SQL querying of PostgreSQL database tables and data
Why this server?
Provides access to SAS Data Sets containing PostgreSQL data through SQL queries.
Why this server?
Listed as a supported data source for integration through the CData JDBC driver.
Why this server?
Listed as a supported data source in the compatibility table, enabling access to PostgreSQL data.
Why this server?
Provides read-only access to PostgreSQL database data.
Why this server?
Allows SQL querying of PostgreSQL relational database tables and data
Why this server?
Allows querying of PostgreSQL relational database tables and records
Why this server?
Enables SQL-based access to PostgreSQL databases, with tools for listing tables, columns, and executing queries against live PostgreSQL data.
Why this server?
Allows standard SQL connectivity and querying of PostgreSQL database systems.
Why this server?
Enables direct SQL access to PostgreSQL database systems.
Why this server?
Provides read-only access to PostgreSQL databases, allowing querying of tables and columns through SQL SELECT statements. The server exposes PostgreSQL data as relational SQL models that can be retrieved through natural language queries.
Why this server?
Enables direct SQL queries against PostgreSQL databases for comprehensive data access
Why this server?
Enables native SQL access to PostgreSQL databases and tables.
Why this server?
Allows access to PostgreSQL database data through SQL queries
Why this server?
Enables connection to PostgreSQL databases for SQL-based querying.
Why this server?
Enables SQL access to PostgreSQL database systems, allowing querying of relational data stored in PostgreSQL instances
Why this server?
Listed as a supported data source that can be connected to through the CData JDBC driver.
Why this server?
Allows querying of PostgreSQL database systems through SQL interface
Why this server?
Allows querying of PostgreSQL relational databases through SQL interface
Why this server?
Enables SQL-based access to PostgreSQL database tables and records.
Why this server?
Provides access to PostgreSQL database data through SQL queries.
Why this server?
Allows SQL querying of PostgreSQL database systems, providing access to tables, views, and relational data stored in PostgreSQL instances.
Why this server?
Provides tools for querying PostgreSQL relational database through SQL interface for data retrieval and analysis
Why this server?
Listed as a supported data source that can be queried through the MCP server.
Why this server?
Provides access to PostgreSQL database tables and data through SQL.
Why this server?
Enables SQL queries against PostgreSQL database data through CData's JDBC driver
Why this server?
Enables access to PostgreSQL database data through relational SQL models, supporting table discovery, column information retrieval, and SQL query execution.
Why this server?
Enables SQL querying of PostgreSQL database tables, views, and stored procedures
Why this server?
Provides read-only access to PostgreSQL data by exposing tables as relational SQL models, allowing retrieval of live data through simple MCP queries.
Why this server?
Enables querying of PostgreSQL database data through standard SQL operations, providing access to relational database information.
Why this server?
Allows accessing PostgreSQL database data through SQL queries.
Why this server?
Listed as a supported data source that can be integrated with the MCP server for data access.
Why this server?
Allows direct SQL access to PostgreSQL databases
Why this server?
Allows direct querying of PostgreSQL database tables and data.
Why this server?
Provides access to PostgreSQL database data through SQL-based tools for listing tables, retrieving column information, and executing SELECT queries.
Why this server?
Provides direct SQL querying access to PostgreSQL database tables and relational data.
Why this server?
Listed as a supported data source that can be connected to through the CData JDBC driver.
Why this server?
Provides read-only access to PostgreSQL database through SQL queries, enabling retrieval of relational database content
Why this server?
Listed as a supported data source that can be integrated with the MCP server for querying PostgreSQL data.
Why this server?
Listed as a supported data source for querying PostgreSQL databases.
Why this server?
Listed as a supported data source that can be connected to through the CData JDBC driver, enabling data querying capabilities.
Why this server?
Allows querying PostgreSQL database tables and data through SQL.
Why this server?
Allows direct SQL access to PostgreSQL database systems.
Why this server?
Listed as a supported data source for integration, allowing access to PostgreSQL data through the MCP server.
Why this server?
Listed as a supported data source for integration, allowing access to PostgreSQL databases.
Why this server?
Allows querying of PostgreSQL data by exposing it as relational SQL models through the CData JDBC Driver.
Why this server?
Listed as a supported data source that can be accessed through the CData JDBC driver, allowing for data retrieval from PostgreSQL database.
Why this server?
Provides read-only access to PostgreSQL data through SQL models, allowing queries of PostgreSQL data through natural language requests.
Why this server?
Listed as a supported data source that can be integrated with the MCP server for retrieving data.
Why this server?
Enables querying of PostgreSQL databases through SQL interfaces initiated by natural language questions.
Why this server?
Provides access to PostgreSQL database data by exposing it as queryable SQL tables through the MCP server.
Why this server?
Provides read-only SQL access to PostgreSQL databases, tables, and data.
Why this server?
Provides native SQL access to PostgreSQL databases, enabling queries against tables and data.
Why this server?
Provides read-only access to PostgreSQL database through SQL queries, enabling retrieval of relational database information
Why this server?
Enables SQL-based access to PostgreSQL databases.
Why this server?
Enables direct SQL access to PostgreSQL database tables, views, and stored procedures.
Why this server?
Allows SQL-based access to PostgreSQL databases and tables.
Why this server?
Listed as a supported data source for integration, enabling access to PostgreSQL database data through the CData JDBC Driver.
Why this server?
Provides SQL-based access to PostgreSQL data, enabling retrieval of relational database information through natural language questions.
Why this server?
Provides read access to PostgreSQL database data through SQL interfaces, enabling natural language querying of relational database information.
Why this server?
Manages PostgreSQL database services deployed through Coolify's service management capabilities
Why this server?
Allows direct interaction with YugabyteDB (PostgreSQL-compatible) databases, providing tools for listing tables with schemas and row counts, and executing read-only SQL queries with results returned as JSON.
Why this server?
Provides database storage for project and task management data, allowing persistent storage and retrieval of project information through Prisma ORM
Why this server?
Provides integration with PostgreSQL databases for storing prompts, with export/import functionality and synchronization between file storage and database
Why this server?
Offers database schema specifications for PostgreSQL (as part of Supabase) to store and query Quranic etymology data
Why this server?
Enables connection to PostgreSQL databases with support for authentication, SSL connections, and execution of SQL queries against PostgreSQL 9.5 or later.
Why this server?
Enables natural language queries to PostgreSQL databases with read-only access for schema inspection, table listing, and SQL query execution with built-in safety checks
Why this server?
Provides tools for direct PostgreSQL database operations, including executing SQL queries, viewing database connections and statistics, listing extensions, and querying system catalogs.
Why this server?
Provides access to PostgreSQL database schemas and metadata, enabling users to list tables, describe table schemas, explore foreign key relationships, view available schemas, and get index information for tables.
Why this server?
Provides AI assistants with secure, structured access to PostgreSQL databases. Includes tools for querying, inserting, updating, and deleting data with schema introspection, filtering, pagination, sorting, and safety features.
Why this server?
Supports natural language queries to PostgreSQL databases with intelligent SQL conversion and table structure retrieval
Why this server?
Connects to a PostgreSQL database containing TeslaMate data to retrieve and analyze Tesla vehicle information.
Why this server?
Enables direct SQL execution against PostgreSQL databases with connection pooling, safe query generation, and parameterized queries. Supports searching, retrieving, and managing data in Postgres databases through SQL statements defined in YAML configuration.
Why this server?
Enables creation and management of PostgreSQL databases through Coolify
Why this server?
Provides tools for working with PostgreSQL databases in Supabase, including listing tables, extensions, executing SQL queries, viewing active connections, and accessing database statistics.
Why this server?
Integrates with PostgreSQL database (with pgvector extension) to store and retrieve various memory types with vector embeddings for semantic similarity search
Why this server?
Allows execution of SQL queries on PostgreSQL databases with configurable read-only or write access permissions, returning structured results with metadata
Why this server?
Provides PostGIS database connection capabilities, allowing spatial data querying and manipulation through PostgreSQL with the PostGIS extension.
Why this server?
Offers tailored prompt suggestions for PostgreSQL database design and development
Why this server?
Stores and retrieves news articles that are exposed through the news MCP server's API. Articles are categorized by topics like tech, data science, and cybersecurity.
Why this server?
Provides domain-specific API access to PostgreSQL databases, specifically optimized for the RAGmonsters dataset with custom query operations
Why this server?
Converts Parquet files to PostgreSQL tables with pgvector support for vector similarity search
Why this server?
Enables database interaction with PostgreSQL, with a dedicated template for handling database operations
Why this server?
Provides a secure read-only interface to PostgreSQL databases, allowing execution of validated SELECT queries with timeout protection
Why this server?
Provides tools for exploring and querying a PostgreSQL database, including executing read-only SQL queries, listing tables, and obtaining schema information for specific tables.
Why this server?
Supports PostgreSQL as a database backend for storing MCP server registrations and configuration data.
Why this server?
Used as the database backend for storing user interactions and tracking data for the AI customer support system.
Why this server?
Stores user interactions, context metadata, and tracking data for the AI customer support system.
Why this server?
Optional database backend that can be configured to replace the default SQLite database
Why this server?
Provides connection to PostgreSQL databases, allowing AI agents to query and work with PostgreSQL data
Why this server?
Allows querying clinical trial data from the AACT database (which contains ClinicalTrials.gov information) stored in PostgreSQL, with tools for exploring database tables, executing SELECT queries, and recording analytical insights.
Why this server?
Integrates with PostgreSQL databases, specifically with the Apache AGE extension that enables graph database capabilities in PostgreSQL. Allows querying, creating, and managing graph data structures.
Why this server?
Provides comprehensive read-only access to PostgreSQL databases with multi-tenant support, enabling schema introspection, table structure analysis, function definition retrieval, and flexible SQL querying across different tenant schemas.
Why this server?
Provides comprehensive PostgreSQL database analysis and optimization tools including health monitoring, performance tuning, index recommendations, and maintenance planning.
Why this server?
Stores text and vector embeddings using the pgvector extension, enabling efficient similarity searches and knowledge base retrieval.
Why this server?
The MCP server supports PostgreSQL with pgvector as a production-ready storage backend option for the knowledge base
Why this server?
Allows querying PostgreSQL databases, browsing tables, viewing schema information, and running read-only SQL queries with safety checks.
Why this server?
Provides direct SQL access to PostgreSQL databases, tables, and data.
Why this server?
Listed as a supported data source for integration through the CData JDBC Driver
Why this server?
Enables SQL querying of PostgreSQL relational database systems and data
Why this server?
Enables direct SQL access to PostgreSQL databases, tables, and data.
Why this server?
Allows querying of PostgreSQL database data by exposing it as relational SQL models through the CData JDBC driver.
Why this server?
Enables SQL access to PostgreSQL databases and tables.
Why this server?
Provides direct SQL querying capabilities for PostgreSQL databases, tables, and relational data structures.
Why this server?
Enables SQL querying of PostgreSQL databases, providing full access to relational data stored in PostgreSQL database systems.
Why this server?
Allows native SQL queries against PostgreSQL databases.
Why this server?
Enables querying of PostgreSQL database tables and data through SQL models.
Why this server?
Listed as a supported data source for integration with the MCP server, allowing access to PostgreSQL data.
Why this server?
Enables direct SQL querying of PostgreSQL database systems for relational data access.
Why this server?
Enables SQL-based access to PostgreSQL databases, allowing queries against relational database tables and views.
Why this server?
Enables querying of PostgreSQL relational databases through SQL operations for advanced database management.
Why this server?
Allows querying PostgreSQL databases through a SQL interface.
Why this server?
Provides direct SQL access to PostgreSQL databases for data retrieval and analysis
Why this server?
Enables access to PostgreSQL databases through SQL queries.
Why this server?
Provides SQL querying capabilities for PostgreSQL database systems, enabling access to relational data stored in PostgreSQL instances.
Why this server?
Listed as a supported data source that can be accessed through CData JDBC Driver and exposed via the MCP server.
Why this server?
Enables direct SQL querying of PostgreSQL database systems.
Why this server?
Allows access to data stored in PostgreSQL databases.
Why this server?
Enables read-only access to PostgreSQL databases through natural language queries rather than SQL commands.
Why this server?
Included in the list of supported sources for data retrieval through the MCP server.
Why this server?
Listed as a supported data source that can be accessed through the MCP server.
Why this server?
Enables direct SQL access to PostgreSQL databases, allowing querying of tables, views, and database objects.
Why this server?
Provides read-only access to PostgreSQL databases through SQL queries, enabling retrieval of relational database data.
Why this server?
Provides read-only access to PostgreSQL database data, allowing retrieval of table information through natural language queries without requiring SQL knowledge.
Why this server?
Provides SQL access to PostgreSQL database systems for advanced relational data querying and analytics
Why this server?
Allows direct SQL access to PostgreSQL databases, enabling queries on relational data stored in PostgreSQL systems
Why this server?
Allows querying PostgreSQL databases through SQL operations, providing full access to advanced relational database features and data.
Why this server?
Offers read-only access to PostgreSQL relational database tables and data.
Why this server?
Enables standard SQL queries against PostgreSQL databases and tables.
Why this server?
Listed as a supported data source that can be accessed through the MCP server interface, allowing retrieval of PostgreSQL data through SQL queries.
Why this server?
Enables querying PostgreSQL databases through SQL operations, providing access to relational database tables and content.
Why this server?
Allows querying PostgreSQL database data through SQL interfaces.
Why this server?
Provides SQL access to PostgreSQL database data, enabling comprehensive database queries and advanced data operations.
Why this server?
Provides SQL-based access to PostgreSQL database content.
Why this server?
Enables SQL-based access to PostgreSQL database data, supporting querying of tables and records.
Why this server?
Offers comprehensive PostgreSQL database support with connection management, data browsing, and manipulation capabilities.
Why this server?
Provides access to Aiven for PostgreSQL services, enabling query execution and database management operations.
Why this server?
Provides advanced interaction with PostgreSQL databases, featuring index tuning, query plan analysis, health diagnostics, workload analysis, and safe SQL execution for both development and production environments
Why this server?
Used for vector storage of memories, allowing semantic indexing and retrieval of stored information
Why this server?
Provides tools for connecting to and interacting with PostgreSQL databases, supporting data querying, modification, and schema operations
Why this server?
Stores collected news data and analysis results in a PostgreSQL database
Why this server?
Serves as the production database storage solution for contexts, templates, and analytics data.
Why this server?
Supports database connectivity for importing, querying, and analyzing data from PostgreSQL databases
Why this server?
Connects to PostgreSQL databases and executes read-only queries, lists tables, and provides schema information.
Why this server?
Provides access to Aiven for PostgreSQL services, allowing interaction with PostgreSQL databases running in the Aiven platform.
Why this server?
Supports connecting to and querying PostgreSQL databases with natural language, including schema analysis and query validation
Why this server?
Provides integration with PostgreSQL as a database backend option for persistence and scalability beyond the default SQLite
Why this server?
Connects to PostgreSQL databases, automatically generates APIs from table schemas, and provides secure access to data with support for complex queries.