planetscale

Query PlanetScale databases via MCP server or pscale CLI for schemas and performance insights.

190|14|Updated May 20, 2014
One-click install
npx skills add https://github.com/elithrar/dotfiles --skill planetscale
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planetscale
Source: https://github.com/elithrar/dotfiles/tree/main/.config/opencode/skill/planetscale
Command: npx skills add https://github.com/elithrar/dotfiles --skill planetscale

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

PlanetScale database management often requires toggling between MCP-based tooling and the pscale CLI to diagnose connections, query schemas, and optimize performance. This skill centralizes those tasks and provides guidance for read queries, schema inspection, and monitoring across Vitess and Postgres backends.

Core Features & Use Cases

  • Unified PlanetScale access: Interact with PlanetScale via MCP or CLI to enumerate databases, branches, and deployments.
  • Troubleshooting & insights: Debug connection errors, view branch schemas, and analyze query performance.
  • Use case: Inspect a multi-environment setup to list databases, confirm a branch schema, and run a read query to validate access.

Quick Start

  • Check MCP availability and list databases: pscale database list --org <org> or use MCP read queries if MCP tools are available.
  • If MCP is unavailable, use the pscale CLI to perform common tasks such as listing databases and branches, opening a shell, or creating a deploy request.
  • See references/cli-commands.md and references/connection-issues.md for deeper troubleshooting steps.

Frequently Asked Questions about planetscale

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug PlanetScale database connection issues?

Debug PlanetScale connections by verifying MCP availability and authentication credentials, then use pscale CLI commands like `pscale database list` or MCP read queries to confirm access. Check references/connection-issues.md for detailed troubleshooting steps covering common authentication and network errors.

Can I inspect a PlanetScale database schema across multiple branches?

Yes. Use pscale CLI or MCP tools to list branches within a database, then query the schema for each branch to compare structure across development, staging, and production environments. This enables validation before merging schema changes across Vitess and Postgres backends.

What's the best way to query PlanetScale databases without leaving the CLI?

Query PlanetScale via pscale CLI shell or MCP server tools to run read queries directly against your database. MCP integration centralizes schema inspection, performance analysis, and connection verification without toggling between separate tools.

Do I need the pscale CLI installed to access PlanetScale databases?

The pscale CLI is one option; MCP tools provide an alternative if configured. The Skill covers both paths—use pscale CLI for local command-line access or MCP for integrated tooling, depending on your environment setup and authentication availability.

How do I analyze query performance across PlanetScale deployments?

Use pscale CLI or MCP read queries to gather performance insights and query patterns from your databases and branches. The Skill guides inspection of multi-environment setups to identify bottlenecks and validate query access across Vitess and Postgres backends.

What authentication do I need to connect to PlanetScale via MCP or CLI?

Provide PlanetScale authentication tokens or credentials for your organization. Both pscale CLI and MCP tools require valid credentials to perform read queries, list databases, and access schema details; configure organization details via `--org` flag or environment variables.