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 Cursor 10 tools — connect in under 2 minutes

Name: PlanetScale
Availability: InStock
Author: Vinkius

docs.cursor.com/context/model-context-protocol

Built by Vinkius GDPR 10 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

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.

Cursor's Agent mode turns PlanetScale into an in-editor superpower. Ask Cursor to generate code using live data from PlanetScale and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

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 Cursor 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 Cursor via MCP

Follow these steps to integrate the PlanetScale MCP Server with Cursor.

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using PlanetScale

Open Agent mode in chat and ask: "Using PlanetScale, help me...". 10 tools available

Why Use Cursor with the PlanetScale MCP Server

Cursor AI Code Editor provides unique advantages when paired with PlanetScale through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

PlanetScale + Cursor Use Cases

Practical scenarios where Cursor combined with the PlanetScale MCP Server delivers measurable value.

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

PlanetScale MCP Tools for Cursor (10)

These 10 tools become available when you connect PlanetScale to Cursor 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 Cursor

Ready-to-use prompts you can give your Cursor 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 Cursor

Common issues when connecting PlanetScale to Cursor through the Vinkius, and how to resolve them.

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

PlanetScale + Cursor FAQ

Common questions about integrating PlanetScale MCP Server with Cursor.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.