Search for:
Why this server?
This server provides a Model Context Protocol (MCP) tool for exploring and managing different types of databases including PostgreSQL.
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?
A NestJS module that allows services to be exposed as an MCP server with Server-Sent Events transport, facilitating tool discovery and execution by clients.
Why this server?
This server implements the Model Context Protocol for seamless interaction with Azure Blob Storage and Cosmos DB, enabling automatic logging and audit tracking of operations.
Why this server?
MCP to access any database accessible via JDBC such as Postgres.
Why this server?
A Model Context Protocol (MCP) server for creating commit messages from git staged files, useful in a NestJS environment.
Why this server?
Enables LLMs to interact with MySQL databases by inspecting schemas and executing safe, read-only queries within transactions.
Why this server?
An MCP server that allows users to interact with YNAB data, enabling access to account balances, transactions, and the creation of new transactions through the Model Context Protocol, which would work well with a NestJS server.
Why this server?
This server provides integration with Timeplus, a database for streaming data, such as Apache Kafka/Pulsar, fitting a modern NestJS backend.