Skip to main content
Glama
supabase-notion MCP Server

supabase-notion MCP Server

by xhq52465840

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_MAX_ROWSNoMaximum row limit for queries.100
NOTION_TOKENNoThe Notion integration token.
SUPABASE_URLNoThe Supabase project URL (for example, https://YOUR-PROJECT.supabase.co).
MCP_READ_ONLYNoWhen true, write tools are not even registered.false
NOTION_PARENT_PAGE_IDNoThe Notion parent page ID used when creating pages.
SUPABASE_ALLOWED_TABLESNoComma-separated list of allowed table names; any other table is refused.
SUPABASE_SERVICE_ROLE_KEYNoThe Supabase service-role key used to access the database.

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

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
supabase_list_tablesA

List the tables this server may access, with their columns and row counts. Call this first to learn the schema.

supabase_queryB

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

supabase_insertA

Insert one or more rows into an allowed table and return the created rows. Confirm with the user before inserting.

notion_searchB

Full-text search over Notion pages the integration can access. Returns id, title, url and last edited time.

notion_get_pageB

Read the plain-text content of a Notion page by id.

notion_create_pageA

Create a new Notion page from markdown (headings, bullet and numbered lists, quotes, paragraphs). Uses NOTION_PARENT_PAGE_ID when parentId is omitted.

Prompts

Interactive templates invoked by user choice

NameDescription
ops_reviewSummarize urgent tickets for key accounts into a Notion page.

Resources

Contextual data attached and managed by the client

NameDescription
supabase-schema

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation4/5

The service prefix (supabase_ vs notion_) immediately separates the two domains, and within each the actions are distinct (list vs query vs insert; search vs get vs create). The only mild overlap is supabase_list_tables vs supabase_query, which the description mitigates by explicitly telling agents to call list_tables first to learn the schema.

Naming Consistency5/5

Every tool follows the same service_verb_noun pattern in snake_case (supabase_list_tables, supabase_query, notion_get_page, etc.), making the grouping and action predictable. No mixed conventions or stray vague verbs.

Tool Count4/5

Six tools is a lean, well-scoped surface for a two-integration bridge, with each tool earning its place. It leans slightly thin for covering two distinct services, but nothing feels redundant or bloated.

Completeness3/5

Supabase offers list/query/insert but no update or delete, and Notion offers search/get/create but no page update, append, or block-level editing, leaving common lifecycle operations unreachable. These are notable gaps that will force agents to dead-end on routine mutation workflows.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues