Retrieve a list of all applied database migrations from the Supabase schema_migrations table to track schema changes.
MIT
778,076 tools. Updated 2026-11-13 19:31
"Checking Supabase migrations in GitHub Actions" matching MCP tools:
- Choose a backend switchover strategy: fully switch to Supabase, keep previews on old backend, park Supabase as backup, or handle manually. Applies the selected method or skips changes.MITDestructive
- Deploy a Supabase backend from a spec after backend_render: migrations, secrets, auth, legal build, edge functions. Dry-run returns plan; live requires human approval.MITDestructive
- Retrieve full production context for a project: GitHub repo, Vercel deployment status, Supabase project, Stripe mode, allowed or blocked actions, audit history, and recommended next steps.MIT
- Run SQL on a Supabase project to apply schema changes or migrations manually; live writes require human approval.MITDestructive
- List connected integrations to retrieve instance IDs for Supabase, GitHub, or Base44 and verify if any source-control account is linked.MIT
Matching MCP Servers
- AlicenseNot gradedqualityDmaintenanceAnalyzes GitHub Actions workflows and performance, helping identify bottlenecks, failures, and optimization opportunities in CI/CD pipelines.19 npmMIT
- FlicenseNot gradedqualityDmaintenanceAudits GitHub Actions workflow files for supply-chain risks like script injection, leaked tokens, unpinned actions, and broad permissions.-
Matching MCP Connectors
- GitHub Actions AuditOAuth
GitHub Actions workflow security audit - 21 checks: pinning, permissions, secrets, injection.
Audit GitHub Actions workflows for script injection, unpinned actions and missing permissions.
- Retrieve detailed information about Supabase database migrations, including version, name, and SQL statements. Use filters for pagination, name patterns, and query inclusion with this low-risk read tool.Apache 2.0
- Retrieve integration settings (Supabase, GitHub, Algolia, etc.) for a FlutterFlow project. Uses cached data from a prior sync; run sync_project first.MIT
- Scans CI/CD workflow files for dangerous secret interpolation in shell commands, detecting log leak and injection risks in GitHub Actions, CircleCI, and GitLab CI pipelines.MIT
- Initiate a dashboard-tracked GitHub publish: commit already-staged changes, push without force, and monitor GitHub Actions in the background.MITDestructive
- List all migrations and filter by status to monitor project transfers from source platforms to Supabase infrastructure.MIT
- Record immutable audit trail entries for blockchain payments and compliance actions. Each entry costs $0.001 USDC and persists in Supabase.MIT
- Scan GitHub Actions workflow files to identify outdated or deprecated actions.MIT
- Scan a GitHub Actions workflow file for dangerous triggers, template injection, unpinned actions, excessive permissions, and secrets in shell commands before committing.MIT
- List all GitHub Actions workflows defined in a repository to gain visibility into CI/CD pipelines for monitoring and management.ISC
- List all GitHub Actions workflows in a repository to review automation pipelines, with pagination support for browsing large collections.MIT
- Trigger a manual sync to detect changes since the last sync and apply database migrations, edge function updates, and frontend changes to your Supabase instance and deployment target.MIT
- Retrieve the cache retention limit for GitHub Actions in a specified organization.MIT
- Lists connected projects, filterable by sync mode, to review GitHub-to-Supabase sync status and spot paused or archived deployments.MIT
- Track and display applied database migrations from the supabase_migrations.schema_migrations table for self-hosted Supabase instances. Useful for managing and verifying database schema changes.ISC
- Retrieve the configured Supabase anon key from a self-hosted MCP server to securely interact with its Supabase instance for database queries, migrations, and feature management.ISC