Zynx Supabase MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZYNX_ENV | Yes | Environment name (e.g., development, staging, production). | |
| SUPABASE_KEY | Yes | Supabase service role or server key. | |
| SUPABASE_URL | Yes | Supabase project URL, e.g., https://your_project.supabase.co. | |
| ZYNX_MAX_LIMIT | Yes | Maximum allowed row limit for queries. | |
| ZYNX_AUDIT_TABLE | Yes | Name of the audit log table. | |
| ZYNX_ENABLE_AUDIT | Yes | Whether audit logging is enabled (true/false). | |
| ZYNX_DEFAULT_LIMIT | Yes | Default row limit for queries. | |
| ZYNX_ALLOWED_TABLES | Yes | Comma-separated list of allowed table names. | |
| ZYNX_MAX_FILE_BYTES | Yes | Maximum file size in bytes for reading workspace files. | |
| ZYNX_WORKSPACE_ROOTS | Yes | Allowed workspace root paths, separated by colons or commas. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_agent_healthA | Check whether the Zynx Supabase MCP server is alive and configured. |
| list_allowed_tablesA | List Supabase tables this MCP server is allowed to read. |
| query_tableA | Read rows from an allowlisted Supabase table with optional equality filters. |
| search_memoryB | Keyword search over an allowlisted Zynx memory table using ilike. |
| add_memoryC | Persist project, research, coding, or automation memory in an allowlisted Supabase table. |
| create_projectB | Create a Zynx project record for orchestration, memory, research, coding, and automation work. |
| list_workspace_filesC | List files inside configured Zynx workspace roots for coding and automation tasks. |
| read_workspace_fileA | Read a small text file inside configured Zynx workspace roots. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct resource-action pair: health, table listing, generic query, memory search, memory write, project create, file listing, and file read. No two tools perform the same operation on the same resource.
All tool names follow a consistent verb_noun pattern in snake_case (get_, list_, query_, search_, add_, create_, read_). The style is uniform and predictable.
With 8 tools, the server covers its core capabilities without bloat. It is within the ideal 3-15 range and each tool serves a clear purpose.
The tool surface is notably incomplete: memory supports add and search but no update or delete; projects support create but no retrieval, update, or delete; workspace files support list and read but no write. These are significant gaps for a server that claims to support orchestration, memory, and automation.