The MCP tool directory.

Get details of a specific Supabase project by reference ID. Returns name, region, status, database host, and API URL.

Generate TypeScript type definitions from the Supabase project database schema. Useful for type-safe database access.

Get a single user by ID from Supabase Auth. Returns full user details including metadata, identities, and last sign-in.

Insert one or more records into a Supabase table. Pass a single object or an array of objects. Use return=representation to get the created records back.

List API keys for a Supabase project. Returns anon key, service_role key, and any custom keys with their names and roles.

List all storage buckets in the Supabase project. Returns bucket name, public status, size limits, and allowed MIME types.

List all Edge Functions deployed to a Supabase project. Returns function slug, name, status, and creation date.

List database migrations for a Supabase project. Shows migration version, name, and status.

List objects (files) in a Supabase storage bucket. Supports prefix filtering, pagination, and search.

List all Supabase projects in your account. Returns project name, ref, region, status, and database info. Requires SUPABASE_ACCESS_TOKEN.

List records from a Supabase table/view with PostgREST filtering, column selection, ordering, and pagination. Filter syntax: age=gt.18, status=eq.active, name=ilike.*john*, id=in.(1,2,3). Resource embedding (JOINs): select=*,orders(*)

List all secrets (environment variables) for a Supabase project. Returns secret names only (values are never exposed).

List all users in the Supabase Auth system. Returns paginated results with user details including email, metadata, and creation date.

Pause a Supabase project. Paused projects stop all services (database, auth, storage) and free up resources. Free tier projects auto-pause after inactivity.

Restore a paused Supabase project. Restarts all services including database, auth, and storage.

Execute a SQL query on a Supabase project database via the Management API. Supports SELECT, INSERT, UPDATE, DELETE, CREATE TABLE, and all SQL. Returns query results as JSON.

Update records in a Supabase table matching a filter. Filter is REQUIRED to prevent accidental full-table updates. Use return=representation to see what changed.

Update a user in Supabase Auth. Can change email, phone, password, metadata, or ban the user.

Upsert (insert or update on conflict) records in a Supabase table. Uses merge-duplicates by default. Specify on_conflict for non-primary-key columns.

Run a full 6-agent VerdictSwarm risk scan. Returns consensus score, risk level, and agent-level findings for safe trading decisions.

Capture screenshots of multiple URLs in one call (max 10). Returns an array of results with screenshot URLs and metadata. All screenshots share the same viewport and format settings.

Capture a URL in Chromium, Firefox, and WebKit simultaneously. Returns three screenshot URLs — one per browser engine. Useful for cross-browser visual testing.

Capture a full-page screenshot with dark mode (prefers-color-scheme: dark) emulated. Works on sites that support dark mode via CSS media queries.

Compare two URLs pixel-by-pixel and return a diff overlay image showing exactly what changed. Returns the diff image URL, percentage of pixels changed, total changed pixel count, and a match score.

Capture a screenshot of a specific element on the page by CSS selector. Only the matched element is captured, not the full page. Automatically waits for the element to appear (SPA-friendly). Use delay for pages that need extra hydration time.

Capture a full-page screenshot (entire scrollable content) of any URL. Use max_height to cap extremely long pages and prevent unreadable strips.

Export a webpage as a PDF document (A4 format with background graphics). Returns a public URL to the PDF file.

Capture screenshots at desktop (1280×800), tablet (820×1180), and mobile (393×852) viewports in one call. By default captures viewport-only (recommended). Set fullPage to true for full-page captures. Returns all three URLs for responsive comparison.

Capture a screenshot at iPad viewport (820×1180). By default captures viewport-only (not the full scrollable page). Set fullPage to true for full-page capture. Returns device name, dimensions, and public image URL.

Perform a search over: - "internal": Perform a semantic search over your entire Notion workspace and connected sources (Slack, Google Drive, Github, Jira, Microsoft Teams, Sharepoint, OneDrive, or Linear). - "users": Perform a search over the Notion users in the current workspace. You can use search when you need to find information which is not already available via other tools, and you don't know where it's located. If the user doesn't have access to Notion AI features, the search will automatically fall back to a workspace search that doesn't use AI or include connected sources. This will be indicated by the "type" field in the response being "workspace_search" instead of "ai_search". Do NOT use search to get information about a Database's integrations, views, or other components. If initial results do not contain all the information you need, you can try more specific queries. After obtaining internal search results, if the user asks for the full contents of a page or database, use the "fetch" tool. This tool only shows some details like a highlight and the URL and title of each search result. To find pages under a Notion database, use this tool and supply the database's URL as the data_source_url parameter. These look like "collection://f336d0bc-b841-465b-8045-024475c079dd". You can get this URL by using the "fetch" tool to view the database and copying the URL from the <data-source url="..."> block. Keep in mind that Notion-flavored Markdown has this concept of a hierarchy of <database> blocks that contain <data-source> blocks, but users aren't familiar with the Notion "Data Source" terminology or product. Prefer to refer to both of them as "databases" in your response to humans to avoid confusion. Examples of searches: 1. Search for information across the workspace: { "query": "quarterly revenue report", "query_type": "internal" } 2. Search within a specific page and its children: { "query": "meeting notes action items", "query_type": "internal", "page_url": "https://www.notion.so/workspace/Team-Hub-1234567890abcdef" } 3. Search within a database's pages: { "query": "design review feedback", "query_type": "internal", "data_source_url": "collection://f336d0bc-b841-465b-8045-024475c079dd" } 4. Search within a specific teamspace: { "query": "project updates", "query_type": "internal", "teamspace_id": "f336d0bc-b841-465b-8045-024475c079dd" } 5. Search for users: { "query": "[email protected]", "query_type": "user" } 6. Find users by partial name: { "query": "sarah", "query_type": "user" } Common use cases: - "What does the sales team require from the product team in the next quarter?" - "Find all meeting notes that mention the new pricing strategy" - "Which pages discuss the API migration project?" - "Find all team members with email addresses ending in @design.company.com" - "What are the latest updates on the mobile app redesign?"