Can I run destructive commands like deleting databases through this AI implementation?

Yes. The integration provides `delete_branch` and `delete_database`. They map directly to infrastructure teardowns. You should scope the Service Token carefully inside the PlanetScale dashboard to avoid catastrophic misinterpretations if your explicit intent is just testing. Deletions via `delete_database` are absolute and irretrievable.

Does `create_branch` replicate and copy my production dataset into the new branch?

No. PlanetScale branches solely duplicate the static underlying DDL structure (schema), exactly like taking a snapshot of empty tables. The new branch boots up free of rows. This design lets your agent freely run `ALTER TABLE` operations independently without crashing the master tables.

How does the agent know which organizational node I am provisioning my branches on?

All queries essentially require the foundational string parameters known as the `org_name`. If unknown, a simple `list_organizations` query reveals the UUID scope dictating your authorized account parameter bounds securely.

PlanetScale MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: PlanetScale
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 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.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

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 PlanetScale and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "planetscale": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 PlanetScale MCP Server

Empower your AI agents to manage your PlanetScale serverless infrastructure seamlessly. Leverage the power of Vitess-backed MySQL without leaving your IDE. Ask your AI to branch a production database for testing, list regions, or drop obsolete schema forks instantly.

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

What you can do

Database Provisioning — Instantly list (list_databases), inspect, create (create_database), or destroy serverless MySQL clusters running across global regions.
Branch Management — Harness PlanetScale's Git-like schema workflows. Direct your LLM to spawn a temporary shadow-test branch cloned from main (create_branch), allowing consequence-free migrations before orchestrating Deploy Requests.
Infrastructure Exploration — Discover strict organizational IDs (list_organizations) and query available physical cloud provider edges (list_regions) to optimize latency targets.

The PlanetScale MCP Server exposes 10 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 PlanetScale to VS Code Copilot via MCP

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

Create MCP config

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

Add the server config

Paste the JSON configuration above

Enable Agent mode

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

Start using PlanetScale

Ask Copilot: "Using PlanetScale, help me...". 10 tools available

Why Use VS Code Copilot with the PlanetScale MCP Server

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

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

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

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

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

PlanetScale + VS Code Copilot Use Cases

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

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

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

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

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

PlanetScale MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect PlanetScale to VS Code Copilot via MCP:

create_branch

Does *not* duplicate data (creates an empty schema clone of the parent) for secure CI testing uncoupled entirely from `main` load balancing layers. Fork a PlanetScale schema mapping to a new isolated Branch

create_database

Creates empty environments ready to execute explicit DDL definitions via non-blocking Deploy Requests. Provision a radically scalable Serverless Database instance

delete_branch

Utilized constantly within CI/CD pipelines following a successful Deploy Request morphing `main` schema structure directly. Purge an obsolete Git-like Schema testing ground

delete_database

Dropping the database effectively wipes terabytes of records scattered globally. Fails fully if unacknowledged connection logic binds it. Destroy a PlanetScale MySQL construct irreversibly

get_branch

Returns access hostnames for code integration. Deconstruct the layout of a single explicit Database Branch

get_database

Analyze core configuration of a specific MySQL cluster logic

list_branches

Essential for migrating schemas without locking production reads/writes. List Development Database Branches mirroring Prod architectures

list_databases

Retrieves explicitly mapping IDs orchestrating distributed Vitess backend shards. List high-availability PlanetScale MySQL DB distributions

list_organizations

Used solely to resolve the foundational string key prerequisite for all subsequent MySQL endpoint management. List root PlanetScale organizational identifiers

list_regions

Critical reference required during new Database/Branch physical provisioning routines. Locate physical edge availability zones supported by Vitess

Example Prompts for PlanetScale in VS Code Copilot

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

"List all physical cloud regions currently exposed by the PlanetScale integration."

"We're starting a new feature. Fork testing branch from the main database 'store-backend'."

"Drop the specific 'staging-01' branch inside the 'web-portal' database."

Troubleshooting PlanetScale MCP Server with VS Code Copilot

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

MCP tools not available

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

PlanetScale + VS Code Copilot FAQ

Common questions about integrating PlanetScale MCP Server with VS Code Copilot.

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.

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.

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.

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.