Neon Connector for Muse
Manage Neon serverless Postgres: projects, branches, databases.
- What
- Manage Neon serverless Postgres: projects, branches, databases.
- Cost
- Free
- Needs
- A Neon API key (Neon console > Account settings > API keys), kept in your Muse's secure vault (never paste secrets here). Note: branch create provisions billable compute and branch delete is irreversible — both need exact-match confirmation; connection strings contain passwords and are masked on display. Neon has a free tier.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A Muse agent skill that manages Neon serverless Postgres infrastructure through the Neon Management API: list projects, inspect one project, list branches, create or delete a branch, and list databases. It manages infrastructure only — SQL queries run over the Postgres wire protocol, so this connector does not run queries. Honest note: branch create and branch delete are HIGH actuations — creating a branch provisions live compute that can incur billable usage, deleting one is irreversible and destroys the branch, its compute endpoint, and its data; both need exact-match confirmation. Connection strings embed database passwords — the CLI masks them on display; never paste a full connection string into chat. Neon has a free tier. Draft: written from Neon's public API docs, not yet live-tested end-to-end — this listing's unverified status reflects that. No secrets in the repo.
Curated by Skill Harbor — free, open-source build (MIT) by @bluman1.
Version:
Install
Prerequisites: A Neon API key (Neon console > Account settings > API keys), kept in your Muse's secure vault (never paste secrets here). Note: branch create provisions billable compute and branch delete is irreversible — both need exact-match confirmation; connection strings contain passwords and are masked on display. Neon has a free tier. No GitHub account needed unless listed here. Install "Neon Connector for Muse" for me. A Muse agent skill that manages Neon serverless Postgres infrastructure: projects, branches, databases (infrastructure only, no SQL queries). Repository: https://github.com/bluman1/muse-connectors/tree/main/connectors/neon 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "neon". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my Neon API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.