Skip to main content
Glama
Zynx Supabase MCP Server

Zynx Supabase MCP Server

Zynx Supabase MCP Server

Real TypeScript MCP server for connecting Zynx agents to Supabase through safe, allowlisted tools.

Tools

  • get_agent_health — check MCP server health

  • list_allowed_tables — show table allowlist and limits

  • query_table — read rows from allowlisted Supabase tables

  • search_memory — keyword search over Zynx memory table

  • add_memory — persist project, research, coding, or automation memory

  • create_project — create a project orchestration record

  • list_workspace_files — list files under configured workspace roots

  • read_workspace_file — read small text files under configured workspace roots

Related MCP server: SupaMCPBuilder

Install

cd zynx-supabase-mcp
cp .env.example .env
npm install
npm run build
npm start

Required .env

ZYNX_ENV=development
SUPABASE_URL=https://YOUR_PROJECT_ID.supabase.co
SUPABASE_KEY=YOUR_SUPABASE_SERVICE_ROLE_OR_SERVER_KEY
ZYNX_ALLOWED_TABLES=zynx_projects,zynx_project_tasks,zynx_memory,zynx_audit_logs,zynx_documents,zynx_vectors,zynx_tool_runs
ZYNX_DEFAULT_LIMIT=10
ZYNX_MAX_LIMIT=100
ZYNX_AUDIT_TABLE=zynx_audit_logs
ZYNX_ENABLE_AUDIT=true
ZYNX_WORKSPACE_ROOTS=/Users/kant/zynx-supabase-mcp
ZYNX_MAX_FILE_BYTES=200000

Use .env.staging.example and .env.production.example as profile templates when those environments are created.

Gemini CLI registration

Option A: command line:

gemini mcp add zynx-supabase node /ABSOLUTE/PATH/TO/zynx-supabase-mcp/dist/index.js

Option B: copy config/gemini-settings.example.json into your Gemini CLI settings and replace values.

Test prompts

Use get_agent_health from zynx-supabase.
Use list_allowed_tables from zynx-supabase.
Use query_table to read 5 rows from zynx_memory.
Search Zynx memory for MCP architecture.
List workspace files from /Users/kant/zynx-supabase-mcp.
Add this project decision to Zynx memory.
Create a Zynx project named Zynx MCP Dev.

Security rules

  • Never expose SUPABASE_KEY in frontend code.

  • Keep .env out of git.

  • Keep ZYNX_ALLOWED_TABLES narrow.

  • Keep ZYNX_MAX_LIMIT small.

  • Prefer read-only database roles/RPC in production.

  • Enable Supabase RLS where possible.

Optional Supabase starter schema

See:

supabase/schema.example.sql

It creates starter tables for:

  • zynx_audit_logs

  • zynx_memory

  • zynx_projects

  • zynx_project_tasks

  • zynx_tool_runs

  • zynx_documents

  • zynx_vectors

See docs/architecture.md for the dev-first plan that still supports staging and production.

Helper script

After npm run build:

./scripts/register-gemini.sh

Available Tools

8 tools
add_memoryAdd Zynx MemoryC

Persist project, research, coding, or automation memory in an allowlisted Supabase table.

Inputs: content (required), kind, metadata, projectId, +1 more.

create_projectCreate Zynx ProjectB

Create a Zynx project record for orchestration, memory, research, coding, and automation work.

Inputs: name (required), status, metadata, description.

get_agent_healthGet Zynx MCP HealthA

Check whether the Zynx Supabase MCP server is alive and configured.

Inputs: no named parameters.

list_allowed_tablesList Allowed Supabase TablesA

List Supabase tables this MCP server is allowed to read.

Inputs: no named parameters.

list_workspace_filesList Workspace FilesC

List files inside configured Zynx workspace roots for coding and automation tasks.

Inputs: depth, limit, dirPath.

query_tableQuery Supabase TableA

Read rows from an allowlisted Supabase table with optional equality filters.

Inputs: tableName (required), limit, select, filters, +1 more.

read_workspace_fileRead Workspace FileA

Read a small text file inside configured Zynx workspace roots.

Inputs: filePath (required).

search_memorySearch Zynx MemoryB

Keyword search over an allowlisted Zynx memory table using ilike.

Inputs: query (required), limit, tableName, contentColumn.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      A production-ready TypeScript MCP server providing basic tools (add, echo, timestamp), resources (server info, greetings, data access), and prompt templates (analyze, code-review, summarize). Serves as a foundation for building custom MCP servers with extensible architecture.
      547 npm
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A runtime-configurable MCP server for Supabase databases that enables dynamic tool creation through JSON configuration. Build custom database operations (select, insert, update, delete) without writing code, with built-in authentication and template support.
      10 npm
      11
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A production-grade TypeScript MCP server that provides AI agents with structured access to real-world data across financial markets, Web3/DeFi, developer tools, and healthcare domains. It features built-in authentication, domain isolation, caching, and rate limiting for reliable API integrations.
      MIT