PlugWiki

Neon Functions Skill for Claude Code: What It Does and How to Install It

Makes your assistant build and deploy long-running Node.js functions onto a Neon branch, next to your database.

Installs
32.5K
on skills.sh
Stars
108
on GitHub
Files
8
besides SKILL.md
Updated
Oct 2026
last repo commit

SKILL.md declares functions in neon.ts, runs them locally with neon dev and deploys them with neon deploy. Each function gets a public HTTPS URL, runs in the branch's region and gets DATABASE_URL injected.

It loads when you ask for a long-running function, a WebSocket or SSE server, a webhook handler, an MCP server or a cron trigger. It needs the Neon CLI and a project in one of four AWS regions. It bundles 8 reference files and points to the parent neon skill first.

Good for

  • Developers hosting an API, webhook handler or bot next to a Neon database
  • Teams running streaming AI agents that would time out on short serverless functions
  • People adding cron or upload triggers to a function

Install neon-functions

Claude Code

  1. 1

    Copy this prompt.

    Install the neon-functions skill in Claude Code. Run this command:
    
    npx skills add neondatabase/agent-skills --skill neon --skill neon-functions
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js, A Neon account.

Install the parent neon skill with this one: SKILL.md starts with 'Use the parent neon skill', and the commands here use the Neon CLI. The parent neon skill gives the CLI install (npm i -g neon, plus bun, pnpm or brew variants) and sign-in (neon login). The plugin route installs the neon-postgres plugin: 9 skill folders and the Neon MCP server (https://mcp.neon.tech/mcp), which asks you to sign in with Neon over OAuth on first use. The folder routes copy skills only. There is no Claude app upload route because the skill drives the Neon CLI.

Built from the package data we hold. Not yet tested by us.

What's in the skill

When it loads

Long-running, serverless Node.js HTTP functions deployed onto your Neon branch, with DATABASE_URL injected automatically and compute that runs next to your data. Use when a user wants to host an API, an AI agent with long streaming responses, a WebSocket or server-sent-events (SSE) server, a webhook handler, a Discord bot, an MCP server, or any request/response workload that risks timing out on short, lambda-style serverless functions — and wants it to branch with their database. Also use for Function Triggers: a cron or an object-storage event that POSTs to a function. Triggers include "serverless function", "deploy an API", "long-running function", "streaming agent", "SSE server", "WebSocket server", "webhook handler", "MCP server", "cron", "scheduled function", "object storage trigger", "on upload", "function that won't time out", "function logs", "Neon Functions", "Neon Compute", "DDoS protection", "rate limiting", and "production hardening". For live UIs over database rows, use neon-realtime.

Sections in SKILL.md

  1. When to Use
  2. What It Does
  3. Availability
  4. Architecture: Where Functions Fit
  5. Production hardening
  6. Setup
  7. Develop Locally and Deploy
  8. Native binaries and custom builds
  9. Neon Infrastructure as Code (neon.ts)
  10. Environment Variables
  11. Connecting to Postgres
  12. Timeouts and Runtime Limits
  13. Functions as an Agent Backend (Next.js and Similar Frameworks)
  14. WebSocket Servers
  15. Heartbeat (keep the socket alive)
  16. Fan-out across isolates (do not skip this)

Key facts

Installs on skills.sh
32,534 (Nov 2, 2026)
Last repo commit
Oct 30, 2026

What it includes

  • Confirms the project is in one of four AWS regions before setup.

    Read · Availability check

  • Declares each function by slug and source file in neon.ts.

    The slug cannot change after the first deploy.

    Try: “Deploy a todo API as a Neon Function.”

    Write · neon.ts functions

  • Serves every function in neon.ts locally with hot reload.

    Runs code · neon dev

  • Deploys all functions from neon.ts, reading Function env from the file.

    neon functions deploy <slug> --src deploys a single function.

    Runs code · neon deploy --env <file>

  • Authenticate callers with a JWT or API key, since the URL is public.

    SKILL.md says never to deploy an unauthenticated agent.

    Write · Function auth

  • Long-lived connections, heartbeat, fan-out across isolates, reconnect.

    Write · WebSocket servers and SSE

  • A cron or an object-storage event that POSTs JSON to a function.

    Runs code · Function Triggers

  • Hosts an MCP server as a function, guarded with Managed Better Auth.

    Write · MCP servers on Functions

  • externalPackages installs packages such as sharp for the linux-arm64 runtime.

    Write · Native binaries and custom builds

  • Reads built-in branch logs for functions.

    Runs code · neon logs query --source function

From the official docs

Permissions

Medium risk

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • Deployed functions are public

    SKILL.md says a Neon Function has a public HTTPS URL reachable by anyone, so you must authenticate callers yourself. Check the auth code before you deploy. github.com

  • Secrets travel in an env file

    neon deploy --env <file> reads Function secrets from your gitignored .env file. SKILL.md also lists neon functions deploy --env KEY= which deletes a key. github.com

  • Runs next to your database

    With Postgres on the branch, DATABASE_URL is injected, so function code can read and write your data. Use the unpooled URL only where SKILL.md says it is needed. github.com

Technical details
Turning on read-onlyNo read-only mode is documented for this skill.
Talks toNeon API and the deployed function URL (https, wss)
Sign-in and keysUses your Neon CLI sign-in or API key; Function secrets come from the env file you pass to deploy.
Scopes
  • Runs the Neon CLI as your Neon account

  • Deploys code to a public HTTPS URL on your Neon branch

  • Passes Function secrets from an env file with --env

  • Can set up cron and storage triggers that call a function

Questions

What does the neon-functions skill do?

It helps your assistant build and deploy long-running Node.js HTTP functions on a Neon branch. DATABASE_URL is injected, and the functions suit APIs, streaming agents, WebSocket and SSE servers, webhooks and MCP servers.

How do I install it?

Use the install box at the top of this page. It installs the parent neon skill with this one, because SKILL.md starts by pointing to the neon skill. You also need the Neon CLI and a Neon account.

Is it the official Neon skill?

Yes. It is in Neon's own agent-skills repo, and the repo's marketplace file calls its plugins official Neon plugins for Claude Code.

Does it work in the Claude app?

The install box has no Claude app upload route, because the skill drives the Neon CLI on your machine.

How is it different from Vercel or Lambda functions?

SKILL.md says these functions are long-running and do not time out like lambda-style serverless, with a 15-minute budget for waitUntil work. It also says Neon is backend primitives, not app hosting, and recommends a frontend host such as Vercel for the app.

Where is it available?

SKILL.md says Functions is currently available in aws-us-east-2, aws-us-east-1, aws-eu-central-1 and aws-ap-southeast-1.

Is it safe?

It deploys code to a URL anyone can reach, with your database URL available inside. Our advice: put authentication in place first, and test on a preview branch.

Information

updated Nov 2, 2026

Folder
skills/neon-functions

neondatabase/agent-skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 6
  1. neondatabase/agent-skills README · github.com
  2. neon marketplace.json · github.com
  3. neon plugin.json · github.com
  4. neon mcp.json · github.com
  5. neon SKILL.md (parent skill) · github.com
  6. neon-functions SKILL.md · github.com

Updated Nov 2, 2026.