🌩️ Databases Storm - Unified Database Management System

What is Databases Storm?

Databases Storm is an MCP server that orchestrates Supabase and other databases (Redis, MongoDB, ChromaDB, TimescaleDB, Elasticsearch) to create a unified data management ecosystem. It is designed for developers managing multiple projects and databases, offering centralized control, backup, monitoring, and multi-project management.

How to use Databases Storm?

Clone the repository, install dependencies with npm install, start a local Supabase instance with npm run supabase:start, then launch the server with npm run dev. The server exposes TypeScript commands for Supabase project management, database operations, backup, and migration, and a configuration file (storm-config.yaml) to define projects and additional databases.

Key features of Databases Storm

• Multi-project Supabase instance management
• Integration with Redis, MongoDB, ChromaDB, TimescaleDB, Elasticsearch
• Cross-database backup with encryption and compression
• Unified monitoring with Prometheus and Grafana
• Row Level Security and centralized secrets management
• Admin dashboard showing project status, health, and usage

Use cases of Databases Storm

• Create tenant isolation for a SaaS application with Supabase RLS
• Set up a complete backend for a mobile app with social auth and storage
• Deploy an AI stack using Supabase plus a vector database for RAG
• Migrate a Firebase project to Supabase with a single command
• Orchestrate multi-database deployments for microservices

FAQ from Databases Storm

What runtime does Databases Storm require?

Node.js 20.x and TypeScript 5.x, with Docker for local Supabase and additional databases.

What data is stored and where?

Supabase projects contain PostgreSQL data, authentication, storage, and realtime subscriptions. Additional databases (Redis, MongoDB, etc.) are configured per project. All data resides in local or cloud instances as defined in the YAML config.

Does Databases Storm support authentication providers?

Yes, it can configure JWT, OAuth (GitHub, Google), and Magic Links via Supabase's built-in authentication service.

What transports or authentication does the MCP server use?

The README does not specify transports or authentication for the MCP server itself, but Supabase authentication is managed through JWT and OAuth.

Are there any known limitations?

No limitations are stated in the README. The project is under active development with a roadmap including cloud integration and multi-region replication.