Search for:
Why this server?
This MCP server provides tools for interacting with Supabase databases, storage, and edge functions, implying potential write access capabilities.
Why this server?
Connects to Supabase PostgreSQL databases, exposing table schemas and tools for data analysis through SQL queries which could involve write operations.
Why this server?
Enables querying Supabase databases and generating TypeScript types, implying interaction and possible write functionalities
Why this server?
Enables interaction with CouchDB databases, providing tools for creating, reading, and querying databases and documents implying write access
Why this server?
Allows connection to ClickHouse databases, supporting resource listing, schema retrieval, and query execution, indicating potential for write operations.
Why this server?
This server enables interaction with Azure Blob Storage and Cosmos DB, enabling operations which imply write access, like creating and updating data.
Why this server?
Enables AI assistants to manage Xano databases, allowing users to create, modify, and delete tables, edit schemas, implying write access.
Why this server?
Allows AI assistants to list tables, read data, and execute SQL queries through a controlled interface, which might include write queries.
Why this server?
Provides read-only access to PostgreSQL databases. Since this server alone does not offer write access, it's not ideal, but the user can check whether it can be configured for write.
Why this server?
Allows running SQL queries against SQLite databases, giving the ability to create, read, update, and delete records through SQL commands.