2,500+ MCP servers ready to use
Vinkius

Supabase Alternative MCP Server for VS Code Copilot 14 tools — connect in under 2 minutes

Built by Vinkius GDPR 14 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Supabase Alternative and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "supabase-alternative": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Supabase Alternative
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Supabase Alternative MCP Server

Connect your Supabase account to any AI agent and take full control of your backend infrastructure through natural conversation.

GitHub Copilot Agent mode brings Supabase Alternative data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 14 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

  • Project Management — List, create, pause and restore Supabase projects across regions
  • Branch Operations — Create development branches for preview environments with isolated databases
  • Secret Management — List, create and delete project secrets (API keys, credentials) securely
  • PostgreSQL Configuration — View and update Postgres server settings (max_connections, work_mem, etc.)
  • Organization Discovery — List all organizations and their member projects

The Supabase Alternative MCP Server exposes 14 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Supabase Alternative to VS Code Copilot via MCP

Follow these steps to integrate the Supabase Alternative MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Supabase Alternative

Ask Copilot: "Using Supabase Alternative, help me..."14 tools available

Why Use VS Code Copilot with the Supabase Alternative MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Supabase Alternative through the Model Context Protocol.

01

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Supabase Alternative + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Supabase Alternative MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Supabase Alternative MCP Tools for VS Code Copilot (14)

These 14 tools become available when you connect Supabase Alternative to VS Code Copilot via MCP:

01

create_branch

The branch gets an isolated copy of the database that can be modified independently. Returns the created branch with its name and status. Create a new branch for a Supabase project

02

create_project

Requires the project name, organization ID and optionally the region (e.g. "us-east-1", "eu-west-2") and database password. The project will be provisioned with Postgres, Auth, Storage and API services. Returns the created project with its ref. Create a new Supabase project

03

create_secret

Requires the secret name and value. Optionally set the branch slug (defaults to main). The secret value is encrypted at rest. Returns confirmation of creation. Create a secret for a Supabase project

04

delete_secret

Provide the project ref and secret name. WARNING: the secret cannot be recovered after deletion. Delete a secret from a Supabase project

05

get_postgres_config

Get PostgreSQL configuration for a Supabase project

06

get_project

Provide the project ref (e.g. "abcxyz123456"). Get details for a specific Supabase project

07

get_user

Returns user ID, email, name and account metadata. Use this to verify your token is working correctly. Get the authenticated Supabase user

08

list_branches

Branches are isolated copies of the project database used for preview environments and development. Returns branch name, status, creation date and parent branch info. List branches for a Supabase project

09

list_organizations

Each organization can contain multiple projects. Returns organization ID, name and creation date. List Supabase organizations

10

list_projects

Each project is an isolated instance with its own Postgres database, Auth, Storage and Edge Functions. Returns project ref, name, region, organization ID, creation date and status. List Supabase projects

11

list_secrets

Optionally filter by branch slug. Secrets are used to store API keys, credentials and configuration values securely. List environment secrets for a Supabase project

12

pause_project

The project's database and data are preserved. Provide the project ref. The project can be restored later using restore_project. Pause a Supabase project

13

restore_project

The project's data is fully intact. Provide the project ref. Restore a paused Supabase project

14

update_postgres_config

Provide the project ref and a JSON object with the settings to change (e.g. {"max_connections":200,"work_mem":"16MB"}). Changes may require a database restart. Update PostgreSQL configuration for a Supabase project

Example Prompts for Supabase Alternative in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Supabase Alternative immediately.

01

"Show me all my Supabase projects and their regions."

02

"Create a new dev branch called 'feature-auth' for my staging-api project."

03

"Pause my dev-sandbox project to save costs."

Troubleshooting Supabase Alternative MCP Server with VS Code Copilot

Common issues when connecting Supabase Alternative to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Supabase Alternative + VS Code Copilot FAQ

Common questions about integrating Supabase Alternative MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Connect Supabase Alternative to VS Code Copilot

Get your token, paste the configuration, and start using 14 tools in under 2 minutes. No API key management needed.