
Claimable Postgres
- 7 installs
- 621 repo stars
- Updated August 3, 2026
- neondatabase/mcp-server-neon
Helps with databases tasks during AI-assisted development.
About
claimable-postgres is a Claude Code skill for databases. It helps solo builders move faster with AI-assisted coding.
- claimable-postgres
- Databases
- AI-coding skill
Claimable Postgres by the numbers
- 7 all-time installs (skills.sh)
- Ranked #682 of 911 Databases skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/neondatabase/mcp-server-neon --skill claimable-postgresAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 7 |
|---|---|
| repo stars | ★ 621 |
| Last updated | August 3, 2026 |
| Repository | neondatabase/mcp-server-neon ↗ |
What it does
Helps with databases tasks during AI-assisted development.
Files
Claimable Postgres
Create an instant Postgres database with Claimable Postgres by Neon (pg.new) for fast local development, demos, prototyping, and test environments.
Databases are temporary by default (typically 72 hours) and can be claimed later to a Neon account for permanent use.
Quick Start
Run:
npx get-dbThis provisions a database and writes DATABASE_URL to .env.
When to Use Which Method
CLI (npx get-db)
Use this by default for most users who want a fast setup in an existing project.
npx get-dbCommon flags:
-y, --yes: skip prompts-e, --env <path>: choose env file path-k, --key <name>: customize env var key (defaultDATABASE_URL)-s, --seed <path>: run SQL seed file-L, --logical-replication: enable logical replication-r, --ref <id>: set source/referrer id
SDK (get-db/sdk)
Use this for scripts and programmatic provisioning flows.
import { instantPostgres } from "get-db/sdk";
const db = await instantPostgres();
console.log(db.connectionString);REST API
Use this for non-Node environments or custom integrations.
curl -X POST https://pg.new/api/v1/database \
-H "Content-Type: application/json" \
-d '{"ref":"my-app"}'Agent Workflow
1. Confirm user wants a temporary, no-signup database. 2. Ask whether they want CLI, SDK, or API (default to CLI). 3. If CLI, run npx get-db in the project root. 4. Verify DATABASE_URL was added to the intended env file. 5. Offer a quick connection test (SELECT 1) in their stack. 6. Explain expiry and how to keep it via claim URL.
Output to Provide to the User
Always return:
- where the connection string was written (for example
.env) - which variable key was used (
DATABASE_URLor custom key) - whether a
PUBLIC_CLAIM_URLis present - a reminder that unclaimed DBs are temporary
Safety and UX Notes
- Do not overwrite existing env files; update in place.
- Ask before destructive seed SQL (
DROP,TRUNCATE, massDELETE). - For production workloads, recommend standard Neon provisioning instead of temporary claimable DBs.
- If users need long-term persistence, instruct them to open the claim URL immediately.