Search for:
Why this server?
This server provides a standardized way for MCP clients to interact with Apache Airflow's REST API, supporting operations like DAG management and monitoring Airflow system health.
Why this server?
A powerful Model Context Protocol (MCP) tool for exploring and managing different types of databases including PostgreSQL, MySQL, and Firestore.
Why this server?
MCP to access any database accessible via JDBC such as Postgres, Oracle, mysql, mariadb, sqlite etc.
Why this server?
Enables LLMs to interact with MySQL databases by inspecting schemas and executing safe, read-only queries within transactions.
Why this server?
A Model Context Protocol server providing LLMs read-only access to PostgreSQL databases for inspecting schemas and executing queries.
Why this server?
This server enables interaction with Supabase PostgreSQL databases through the MCP protocol, allowing seamless integration with Cursor and Windsurf IDEs for secure and validated database management.
Why this server?
Enables AI models to perform MySQL database operations through a standardized interface, supporting secure connections, query execution, and comprehensive schema management.
Why this server?
A Model Context Protocol (MCP) server that enables LLMs to interact directly with MongoDB databases. Query collections, inspect schemas, and manage data seamlessly through natural language.
Why this server?
This is an MCP server for PostgREST. It allows LLMs perform database queries and operations on Postgres databases via PostgREST. This server works with both Supabase projects (which use PostgREST) and standalone PostgREST servers.
Why this server?
This server allows AI language models to interact with MySQL databases through a standardized interface.