supabase-notion MCP Server

Query a Supabase table

supabase_query

Read-only

Select rows from allowlisted Supabase tables with optional columns, filters, ordering, and limits to retrieve targeted data.

Instructions

Select rows from an allowed table with optional column list, filters (eq, neq, gt, gte, lt, lte, like, ilike, in), ordering and limit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "table": "<table>"
    },
    "name": "supabase_query"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`table`	Yes	One of: customers, support_tickets, leads
`columns`	No
`filters`	No
`orderBy`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 2, 2026

TDQS

B3.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

readOnlyHint=true is consistent with 'Select rows', so there is no contradiction. The description adds the useful constraint that only an allowed table set can be queried, but it omits practical behavior an agent would want: the default/max row cap (25/100 in schema), and what happens when filters reference non-existent columns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the core action plus optional capabilities come first. The long parenthetical operator list makes it slightly dense but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five parameters, a nested filters/orderBy structure, 20% schema coverage and no output schema, the description covers the surface but not the edges: no return shape (rows array), no pagination/truncation behavior, and no limits on filter count. Adequate to invoke, not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20%, so the description carries more weight; it does map parameter names to concepts (column list, filters, ordering, limit) and lists the filter operators. However, it merely repeats the enum already in the schema and does not explain the low-coverage semantics: limit's default of 25 and max of 100, orderBy's ascending default, or that the 'in' operator requires an array value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Select rows') and resource ('an allowed table') plus the operations supported, which is enough to separate it from supabase_insert (write) and supabase_list_tables (metadata). It never names those siblings explicitly, so differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of when to prefer supabase_list_tables for discovering tables, and no statement of prerequisites or restrictions beyond the phrase 'allowed table'. The agent must infer usage entirely from the verb.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server