Heroku MCP serverofficial
A
securityA
licenseA
qualityLet's your agent access the heroku platform
Last updated -
33
313
42
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 interaction with Aiven for PostgreSQL services, allowing access to database resources hosted on the Aiven platform.
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?
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 tools for accessing and querying PostgreSQL databases through the AgentMode server
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?
Connects to PostgreSQL databases to execute SQL queries and extract analytical insights
Why this server?
Provides PostgreSQL database management capabilities including analysis, setup instructions, and debugging for PostgreSQL database instances
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?
Provides integration with PostgreSQL databases for storing prompts, with export/import functionality and synchronization between file storage and database
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?
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?
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 tools for direct PostgreSQL database operations, including executing SQL queries, viewing database connections and statistics, listing extensions, and querying system catalogs.
Why this server?
Offers tailored prompt suggestions for PostgreSQL database design and development
Why this server?
Converts Parquet files to PostgreSQL tables with pgvector support for vector similarity search
Why this server?
Allows querying PostgreSQL databases, browsing tables, viewing schema information, and running read-only SQL queries with safety checks.
Why this server?
Offers PostgreSQL database creation, configuration, and lifecycle management on Coolify.
Why this server?
Support for PostgreSQL databases is planned in future releases, allowing schema inspection, query execution, and database operations
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?
Connects to PostgreSQL databases, automatically generates APIs from table schemas, and provides secure access to data with support for complex queries.
Why this server?
Allows asynchronous interaction with PostgreSQL databases, including schema discovery, listing databases, tables and views, exploring column details, and executing both structured searches and raw SQL queries.
Why this server?
Connects directly to PostgreSQL databases for query execution, schema exploration, and data analysis
Why this server?
Allows interaction with PostgreSQL databases, providing tools for listing schemas, tables, describing table structures, querying relationships, and executing SQL queries.
Why this server?
Allows querying of PostgreSQL data by exposing it as relational SQL models through the CData JDBC Driver.
Why this server?
The MCP server supports PostgreSQL with pgvector as a production-ready storage backend option for the knowledge base
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?
Offers comprehensive PostgreSQL database support with connection management, data browsing, and manipulation capabilities.
Why this server?
Enables direct SQL access to PostgreSQL database systems.
Why this server?
Allows direct SQL access to PostgreSQL databases
Why this server?
Offers read-only access to PostgreSQL relational database tables and data.
Why this server?
Listed as a supported data source for integration with the MCP server, allowing access to PostgreSQL data.
Why this server?
Allows querying PostgreSQL databases through a SQL interface.
Why this server?
Allows native SQL access to PostgreSQL relational databases.
Why this server?
Listed as a supported data source for querying PostgreSQL databases.
Why this server?
Enables native SQL access to PostgreSQL databases and tables.
Why this server?
Allows querying PostgreSQL database data through SQL interfaces.
Why this server?
Allows access to data stored in PostgreSQL databases.
Why this server?
Provides access to PostgreSQL database data through SQL queries.
Why this server?
Listed as a supported data source for integration through the CData JDBC driver.
Why this server?
Provides read access to PostgreSQL database data through SQL interfaces, enabling natural language querying of relational database information.
Why this server?
Listed as a supported data source in the compatibility table, enabling access to PostgreSQL data.
Why this server?
Provides tools for connecting to and interacting with PostgreSQL databases, supporting data querying, modification, and schema operations
Why this server?
Provides a unified database access interface to PostgreSQL databases, allowing SQL query execution, table structure retrieval, and database analysis capabilities.
Why this server?
Provides read-only access to PostgreSQL databases, allowing LLMs to inspect database schemas and execute read-only queries against connected PostgreSQL databases
Why this server?
Enables querying and interacting with PostgreSQL databases through SQL execution tools and schema resources
Why this server?
Stores user interactions, context metadata, and tracking data for the AI customer support system.
Why this server?
Used as the database backend for storing user interactions and tracking data for the AI customer support system.
Why this server?
Provides tools for AI-optimized interaction with PostgreSQL databases, including schema exploration, query execution, and performance analysis. Enables AI to understand and manipulate database structures with schema-aware context.
Why this server?
Provides read-only access to PostgreSQL databases, enabling SQL queries for tables, views, and relational data.
Why this server?
Allows querying PostgreSQL database tables and data through SQL.
Why this server?
Listed as a supported data source for integration, allowing access to PostgreSQL data through the MCP server.
Why this server?
Allows querying of PostgreSQL databases through relational SQL models.
Why this server?
Listed as a supported data source for integration through the CData JDBC Driver
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?
Provides direct SQL access to PostgreSQL databases, tables, and data.
Why this server?
Enables read-only SQL queries against a PostgreSQL database, with tools for analyzing table statistics and relationships between tables
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?
Enables connection to PostgreSQL databases, with support for querying, schema exploration, and data operations through environment variable configuration.
Why this server?
Provides tools for interacting with PostgreSQL databases, including CRUD operations, schema management (listing databases and tables, describing table structures, creating and altering tables), and executing SQL queries with optional query plan validation and read-only mode protection.
Why this server?
Mentioned as a possible catalog type that can be used with Trino through the MCP server
Why this server?
Provides access to PostgreSQL databases, enabling LLMs to inspect schemas, execute queries, and perform CRUD operations (Create, Read, Update, Delete) on database entries.
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?
Used as the vector database backend for storing and retrieving memories with semantic search capabilities
Why this server?
Allows execution of SQL queries against a PostgreSQL database, access to database schema information, and use of query templates, enabling AI assistants to retrieve and manipulate data in PostgreSQL databases.
Why this server?
Enables SQL execution, schema inspection, and database migration management for PostgreSQL databases
Why this server?
Planned integration for PostgreSQL database operations, including SQL queries, table operations, and schema management.
Why this server?
Supports using PostgreSQL as a database option when scaffolding Payload CMS projects.
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?
Used for storing users, API keys, and transaction records in the MCP blockchain server system
Why this server?
Provides direct access to PostgreSQL databases for executing SQL queries, managing database schemas, and handling transactions with robust safety controls for both read-only and data modification operations.
Why this server?
Provides read-only access to PostgreSQL databases with multi-schema support, allowing inspection of database schemas across multiple namespaces and execution of read-only SQL queries while maintaining schema isolation.
Why this server?
Enables querying PostgreSQL databases, allowing users to retrieve information from configured database instances.
Why this server?
Serves as the robust database backend for storing and retrieving structured data that AI models can access.
Why this server?
Provides tools for querying PostgreSQL database tables, specifically supporting queries for customer FAQs and system menus with filtering capabilities and statistical information retrieval.
Why this server?
Integrates with PostgreSQL database for data persistence and management
Why this server?
Provides a simple interface to interact with PostgreSQL databases, allowing SQL query execution, database operations (INSERT/UPDATE/DELETE), database creation, table schema management, and connection debugging.
Why this server?
Optional database backend for production environments to store enhanced article metadata
Why this server?
Manages user data in a PostgreSQL database, supporting CRUD operations (add, delete, modify, query) for user profiles with details like names and email addresses.
Why this server?
Leverages PostgreSQL (via Supabase) for storing and querying WebDNA documentation with full-text search capabilities
Why this server?
Provides domain-specific API access to PostgreSQL databases, specifically optimized for the RAGmonsters dataset with custom query operations
Why this server?
Enables access to PostgreSQL databases, allowing queries and data operations to be performed through the MCP server
Why this server?
Provides full read-write access to PostgreSQL databases, allowing query execution, data modification, schema management, and detailed database exploration with safety controls and transaction management
Why this server?
Provides advanced database interaction capabilities for PostgreSQL, including detailed schema inspection with metadata, read-only query execution with safety checks, and tools for exploring database structure while enforcing security constraints.
Why this server?
Provides database integration for persistent storage of Sequential Questioning data
Why this server?
Supported as an optional alternative database backend that can be configured by changing the DATABASE_URL environment variable.
Why this server?
Provides tools for executing SQL queries against PostgreSQL databases, including SELECT, CREATE/INSERT, UPDATE, and DELETE operations
Why this server?
Provides read-only SQL query access to an AWS PostgreSQL database, allowing users to execute SELECT queries and retrieve database information through the 'query' tool.
Why this server?
Enables PostgreSQL integration with pgvector extension for storing and querying vectorized data from search results.
Why this server?
Powers the Information Retrieval server for advanced search capabilities, providing both lexical and vector search with pgvector extension.
Why this server?
Provides tools for connecting to, querying, and exploring PostgreSQL databases, including schema discovery, query execution, and analysis of execution plans.
Why this server?
Provides a read-only query interface to PostgreSQL databases, supporting secure connections via SSH bastion tunnels
Why this server?
Provides read-only access to PostgreSQL databases, enabling schema inspection and execution of read-only SQL queries against connected databases.
Why this server?
Enables interaction with PostgreSQL databases, allowing users to list tables, retrieve schemas, and execute read-only SQL queries against PostgreSQL databases.
Why this server?
Provides both read and write access to PostgreSQL databases, allowing for data querying, data modification (insert, update, delete), and schema management (creating tables, functions, triggers, indexes).
Why this server?
Provides database operations for PostgreSQL, enabling CRUD operations on User and Post entities with type-safe queries through the MCP interface
Why this server?
Enables database interaction with PostgreSQL, with a dedicated template for handling database operations
Why this server?
Allows analyzing data from PostgreSQL databases, calculating statistics, and generating ML predictions based on database content
Why this server?
Connects directly to a PostgreSQL database to access and serve Talent profiles with their aesthetic characteristics and design attributes
Why this server?
Provides read-only access to PostgreSQL databases, allowing for schema inspection and execution of read-only SQL queries against connected databases.
Why this server?
Provides vector similarity search capabilities using pgvector extension for efficient storage and retrieval of memory embeddings
Why this server?
Enables direct management of PostgreSQL databases with tools for tables, columns, records, indexes, constraints, functions, triggers, and executing custom SQL queries.
Why this server?
Connects to a PostgreSQL database via MCP, allowing AI models to execute SQL queries with retry logic, view database schema information, and interact with database tables while handling connection errors gracefully.
Why this server?
Provides a secure read-only interface to PostgreSQL databases, allowing execution of validated SELECT queries with timeout protection
Why this server?
Allows creating, configuring, and managing PostgreSQL databases within Coolify, including memory limits, port configuration, and password updates.
Why this server?
Enables interaction with PostgreSQL databases, including connection management, query execution, and transaction handling
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?
Provides database functionality for storing and retrieving educational content and question data
Why this server?
Provides read-only access to PostgreSQL databases, allowing LLMs to inspect database schemas and execute read-only queries
Why this server?
Allows direct interaction with PostgreSQL databases through natural language queries, enabling conversational data exploration and manipulation.
Why this server?
Provides natural language interface to PostgreSQL databases, enabling SQL query generation, schema-aware responses, and read-only data access through the Model Context Protocol.