mcpField
N
neon-toolkit

neon-toolkit

github.com/neondatabaseTesting & quality86164 installsUpdated 39w ago
Repository

About neon-toolkit

A skill for creating, managing, and cleaning up temporary Neon databases with Neon Toolkit. It is intended for tests, CI/CD, and isolated development environments, not production or shared databases.

Key features

  1. 01Create ephemeral Neon databases
  2. 02Manage temporary database lifecycles
  3. 03Clean up databases after use
  4. 04Provide TypeScript workflow templates and scripts
  5. 05Guide project-aware import generation

Use cases

  1. 01Give each test run a fresh database
  2. 02Run tests against temporary databases in CI/CD
  3. 03Create isolated development environments

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/neondatabase/ai-rules --skill neon-toolkit

After installing, type/neon-toolkitin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

scripts/
create-ephemeral-db.ts
destroy-ephemeral-db.ts
templates/
toolkit-workflow.ts

Details

From the project README

Neon Toolkit Skill

Automates creation, management, and cleanup of temporary Neon databases using the Neon Toolkit.

When to Use

  • Creating fresh databases for each test run
  • Spinning up databases in CI/CD pipelines
  • Building isolated development environments
  • Rapid prototyping without manual setup

Not recommended for: Production databases, shared team environments, local-only development (use Docker), or free tier accounts (requires paid projects).

Code Generation Rules

When generating TypeScript/JavaScript code:

  • BEFORE generating import statements, check tsconfig.json for path aliases (compilerOptions.paths)
  • If path aliases exist (e.g., "@/": ["./src/"]), use them (e.g., import { x } from '@/lib/utils')
  • If NO path aliases exist or unsure, ALWAYS use relative imports (e.g., import { x } from '../../../lib/utils')
  • Verify imports match the project's configuration
  • Default to relative imports - they always work regardless of configuration

Reference Documentation

Primary Resource: See [neon-toolkit.mdc](https://raw.githubusercontent.com/neondatabase-labs/ai-rules/main/neon-toolkit.mdc) in project root for comprehensive guidelines including:

  • Core concepts (Organization, Project, Branch, Endpoint)
  • Installation and authentication setup
  • Database lifecycle management patterns
  • API client usage examples
  • Error handling strategies

Quick Setup

Installation
npm install @neondatabase/toolkit
Basic Usage
import { NeonToolkit } from '@neondatabase/toolkit';

const neon = new NeonToolkit({ apiKey: process.env.NEON_API_KEY! });

// Create ephemeral database
const db = await neon.createEphemeralDatabase();
console.log(`Database URL: ${db.url}`);

// Use the database...

// Cleanup
await db.delete();

Templates & Scripts

  • templates/toolkit-workflow.ts - Complete ephemeral database workflow
  • scripts/create-ephemeral-db.ts - Create a temporary database
  • scripts/destroy-ephemeral-db.ts - Clean up ephemeral database

Common Use Cases

Testing
const db = await neon.createEphemeralDatabase();
// Run tests with fresh database
await db.delete();
CI/CD Integration
export NEON_API_KEY=${{ secrets.NEON_API_KEY }}
npm test  # Uses ephemeral database

Related Skills

  • neon-serverless - For connecting to databases
  • neon-drizzle - For schema and migrations

Want best practices in your project? Run neon-plugin:add-neon-docs with parameter SKILL_NAME="neon-toolkit" to add reference links.

Comments

Markdown supported