Search for:
Why this server?
Provides read-only access to PostgreSQL databases, enabling LLMs to inspect database schemas and execute read-only SQL queries.
Why this server?
A Model Context Protocol server that enables performing PostgreSQL database operations (create, read, update, delete) on User and Post entities through MCP tools.
Why this server?
A template project for building custom MCP servers that enables direct access to PostgreSQL databases, allowing SQL query execution and schema information retrieval through the Model Context Protocol.
Why this server?
An HTTP server implementation that enables AI systems to interact with PostgreSQL databases via MCP, providing tools for querying, connecting to multiple databases, and exploring schema resources.
Why this server?
A Model Context Protocol server that enables LLMs to interact with Aiven services (PostgreSQL, Kafka, ClickHouse, Valkey, OpenSearch), enabling LLMs to build full stack solutions by interacting with these services.
Why this server?
The Multi DB MCP Server is a high-performance implementation of the Database Model Context Protocol designed to revolutionize how AI agents interact with databases. Currently supporting MySQL and PostgreSQL databases.
Why this server?
A Model Context Protocol (MCP) server that exposes MiniZinc constraint solving capabilities to Large Language Models. MiniZinc can integrate with postgresql.
Why this server?
Provides integration with Atlassian products through the Model Context Protocol, allowing users to interact with JIRA tickets and Confluence pages.
Why this server?
Enables Cursor and Windsurf to safely interact with Supabase databases by providing tools for database management, SQL query execution, and Supabase Management API access with built-in safety controls.