Skip to content
TrustedSkillsbeta
Back to all skills

Supabase Mcp Integration

Checked
manutej·vlatest·database

Helps with Supabase, MCP tools, integration as part of working with databases and data persistence workflows.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add manutej/crush-mcp-server --skill supabase-mcp-integration -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

manutej

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned manutej/crush-mcp-server at bb8eed14fe.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
4 files, 5,035 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill integrates with Supabase's Managed Cloud Providers (MCP) to allow AI agents to interact directly with your database. It enables automated provisioning and management of cloud resources, simplifying the deployment process for applications relying on Supabase. The integration streamlines tasks such as creating databases, configuring access controls, and managing environment variables within a Supabase project.

When to use it

  • Automated Infrastructure Setup: You need to automatically create and configure new Supabase projects or environments for testing or development.
  • Dynamic Database Provisioning: Your application requires the ability to dynamically provision databases based on user requests or changing requirements.
  • Simplified Development Workflow: You want to streamline your development workflow by automating repetitive tasks related to Supabase resource management.
  • Environment Management: You need a way to manage environment variables and configurations across different Supabase environments programmatically.

Key capabilities

  • Automated MCP provisioning
  • Database creation and configuration
  • Access control management within Supabase
  • Environment variable handling

Example prompts

  • "Create a new Supabase project named 'my-test-project' in the 'us-west-2' region."
  • "Grant read access to the 'public' table in my database to user 'agentuser'."
  • "Set the environment variable 'API_KEY' to 'your_api_key' in the 'staging' environment."

Tips & gotchas

  • Requires appropriate Supabase API keys with sufficient permissions to manage MCP resources.
  • Be mindful of resource limits and costs associated with automated provisioning within your Supabase account.