Retrieve a list of all applied database migrations from the Supabase schema_migrations table to track schema changes.
MIT
556,716 tools. Updated 2026-09-13 06:24
"Checking Supabase migrations in GitHub Actions" matching MCP tools:
- 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
- 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
- Initiate a dashboard-tracked GitHub publish: commit already-staged changes, push without force, and monitor GitHub Actions in the background.MITDestructive
- Record immutable audit trail entries for blockchain payments and compliance actions. Each entry costs $0.001 USDC and persists in Supabase.MIT
Matching MCP Servers
- AlicenseAqualityNot gradedmaintenanceConnects AI assistants to GitHub Actions workflows to monitor CI/CD pipelines, view run logs, diagnose failures, and optionally trigger or manage workflows with granular permission controls.101-
- AlicenseNot gradedqualityDmaintenanceAnalyzes GitHub Actions workflows and performance, helping identify bottlenecks, failures, and optimization opportunities in CI/CD pipelines.32 npmMIT
Matching MCP Connectors
- GitHub Actions AuditOAuth
GitHub Actions workflow security audit - 21 checks: pinning, permissions, secrets, injection.
Your Supabase account in natural language: run SQL, apply migrations, manage tables, storage, edge f
- 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
- Retrieve a list of all GitHub Actions workflows defined in the repository to identify available workflows for local testing.Apache 2.0
- List GitHub Actions workflow runs for a repository in owner/name format, with optional limit and hostname controls, enabling read-only monitoring of CI/CD activity.MIT
- List all GitHub Actions workflows in a repository. Specify owner and repo to get every CI/CD pipeline defined.MIT
- View GitHub Actions workflows in a repository to monitor automation processes and manage CI/CD pipelines.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.-
- 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.-
- View applied database migrations to track schema changes and deployment history in self-hosted Supabase instances.-
- Push local database migrations to your remote Supabase instance on Coolify, ensuring schema changes are applied consistently across environments.MIT
- Check GitHub Actions workflows for errors using actionlint; missing actionlint results in a skipped status.MIT
- Remove GitHub Actions secrets to manage sensitive data in CI/CD pipelines and maintain repository security.-
- List all GitHub Actions workflows in a repository. Provide the owner and repo name to fetch workflow information.-
- Verify Supabase CLI installation and retrieve its version to ensure your environment is ready for database migrations, edge functions, and more.MIT