Frequently Asked Questions (FAQ) about Query MCP Server

Q: What is Query MCP Server?

A: Query MCP Server is an open-source MCP (Model Context Protocol) server that allows you to manage your Supabase projects using a natural language chat interface. It enables you to execute SQL queries, manage schema changes, access logs, and leverage Supabase Management APIs through simple chat commands.

Q: What is MCP (Model Context Protocol)?

A: MCP is an open protocol that standardizes how applications provide context to LLMs. MCP Server acts as a bridge, allowing AI models to access and interact with external data sources and tools.

Q: What is Supabase?

A: Supabase is an open-source Firebase alternative that provides a suite of tools for building scalable and secure applications.

Q: What are the key features of Query MCP Server?

A: Key features include a natural language interface, SQL query execution with risk assessment, schema management with automatic versioning, Supabase Management API support, Auth Admin SDK, and robust safety controls.

Q: What are the benefits of using Query MCP Server?

A: The benefits include increased efficiency, enhanced accessibility, improved safety, and seamless integration with popular MCP clients.

Q: Which MCP Clients are compatible with Query MCP Server?

A: Query MCP Server is compatible with Cursor, Windsurf, Cline, Claude Desktop and any other MCP client that supports the stdio protocol.

Q: What environment variables are required to configure Query MCP Server?

A: Required environment variables include SUPABASE_PROJECT_REF, SUPABASE_DB_PASSWORD, SUPABASE_REGION, and QUERY_API_KEY. Optional variables include SUPABASE_ACCESS_TOKEN and SUPABASE_SERVICE_ROLE_KEY.

Q: How do I install Query MCP Server?

A: You can install Query MCP Server using pipx or uv. Follow the installation instructions in the official documentation.

Q: How do I configure Query MCP Server?

A: Configure the server by setting the necessary environment variables. These can be set directly in your MCP client configuration, in a global .env file, or in a project-specific .env file (if running from source).

Q: How do I find my Supabase project information?

A: You can find your Project Reference in your Supabase project URL (https://supabase.com/dashboard/project/<project-ref>). The Database Password is set during project creation or found in Project Settings → Database. The Access Token can be generated at https://supabase.com/dashboard/account/tokens, and the Service Role Key is found in Project Settings → API → Project API keys.

Q: What safety controls are in place to prevent accidental data loss?

A: Query MCP Server features a three-tier safety system: safe mode (read-only operations), write mode (data modifications), and destructive mode (schema changes). High-risk operations require unsafe mode to be enabled and explicit confirmation.

Q: Does Query MCP Server support local Supabase development?

A: Yes, Query MCP Server supports local Supabase development. The default configuration is set up for local development.

Q: Does Query MCP Server support remote Supabase projects?

A: Yes, Query MCP Server supports remote Supabase projects. You must provide your own values for SUPABASE_PROJECT_REF and SUPABASE_DB_PASSWORD and specify the correct region using SUPABASE_REGION.

Q: What is the UBOS Asset Marketplace?

A: The UBOS Asset Marketplace is a platform that provides a comprehensive suite of tools for AI agent development. It helps you orchestrate AI Agents, connect them with your enterprise data, build custom AI Agents with your LLM model and Multi-Agent Systems.

Q: How does UBOS enhance Query MCP Server?

A: UBOS provides centralized management, seamless integration, enhanced collaboration, and scalable infrastructure for deploying and managing AI agents, including Query MCP Server.

Q: Where can I find more information about Query MCP Server?

A: You can find more information about Query MCP Server in the official documentation on GitHub.

Q: Where can I get an API Key for Query MCP Server?

A: You can get a free API key at thequery.dev.