SupaMCPBuilder

Provides a runtime-configurable MCP server to manage dynamic tools for Supabase databases via JSON configurations.

typescript

GitHub Stars

typescript

Language

5 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "vivek100-supamcpbuilder": {
      "command": "npx",
      "args": [
        "supamcpbuilder",
        "--url",
        "https://your-project.supabase.co",
        "--anon-key",
        "your-anon-key",
        "--email",
        "your-email@example.com",
        "--password",
        "your-password",
        "--tools-json-base64",
        "BASE64_ENCODED_TOOLS"
      ],
      "env": {
        "SUPABASE_URL": "https://your-project.supabase.co",
        "SUPABASE_EMAIL": "your-email@example.com",
        "SUPABASE_ANON_KEY": "your-anon-key",
        "SUPABASE_PASSWORD": "your-password"
      }
    }
  }
}

SupaMCPBuilder lets you run a runtime-configurable MCP server for your Supabase project, enabling dynamic, JSON-defined tools without writing code. It supports automatic authentication handling, template-driven configurations, and base64-encoded tool definitions to safely manage complex setups.

How to use

Start the MCP server from your project workspace using the recommended command. Provide your Supabase project URL, anon key, and your login credentials. You can also pass a base64-encoded JSON configuration to define your tools, or point to a local config file.

How to install

Prerequisites: ensure you have Node.js installed on your machine. You will also need npm to install the MCP package.

Install the MCP globally so you can run it from anywhere.

Run the MCP server directly with npx for quick start or install globally for repeated use.

Configuration and usage notes

Use the command line to start the server with your project credentials. You can supply a base64-encoded tools configuration to define runtime tools, or reference a JSON config file on disk.

Environment variables and credentials are supported for convenience and automation. You can export them in your shell before launching the server.

Security and reliability

Authentication uses email/password with automatic JWT refresh, ensuring your sessions remain valid without manual intervention. All operations respect your Supabase row-level security policies and the system is designed to be secure by default, focusing on user-level operations.

Troubleshooting

If you encounter authentication issues, verify that your email, password, and keys are correct. For permission issues, review your Supabase RLS policies and user roles. Check that your JSON tool configuration is valid and that the Supabase URL is reachable.

Notes

You can run the MCP server via npx for quick tests or install it globally to simplify repeated use. When using a config file, ensure the path is correct and the file is valid JSON.

Built by

VeilStrat

AI signals for GTM teams