Power your agent
पब्लिशर की अपनी कमांड। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
npx -y @neon/[email protected]Claude Code में लोकल कमांड के लिए इंस्टॉल लिंक नहीं है। नीचे दी गई कमांड कॉपी करें और टर्मिनल में चलाएँ।
claude mcp add neon-tools -- npx -y @neon/tools@2.14.2टर्मिनल में चलाएँ।
{ "mcpServers": { "neon-tools": { "command": "npx", "args": [ "-y", "@neon/[email protected]" ] } }}claude_desktop_config.json
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्चपब्लिशर से
The monorepo for Neon's open-source JavaScript/TypeScript SDKs, libraries, CLIs, and framework plugins. Each folder under packages/ is an independently versioned, separately published package; they share tooling (pnpm workspaces, Biome, tsdown, Vitest, Changesets) but ship on their own cadence.
Agent tools for the Neon SDK ergonomic client, compatible with MCP, Eve, and Mastra.
If you're looking for a single package's docs, see its own README.md under packages/<name>/.
Apps and starters that work with these packages live in neondatabase/examples.
neon.ts)neon-new and vite-plugin-neon-new are deprecated. Use Claimable Neon in the Neon CLI: npx neon@latest claim create. The old alias packages (get-db, neondb, vite-plugin-db, @neondatabase/vite-plugin-postgres) still re-export them.
neonctl is not deprecated: it is a supported compatibility package that installs and runs neon.
neon-init is deprecated and no longer built from this repo. Everything it did is the
neon init command, so the command is npx neon init. There is no alias package: it was a
CLI rather than a library, and the replacement is a command on a CLI most users already have.
packages/ # the published SDKs, libraries, CLIs, and plugins (one per folder)
tests/ # test-only tooling that is never published (the live Neon e2e harness)
This is a pnpm workspace. Internal dependencies are linked with workspace:*, so changes to one package are immediately visible to its dependents without republishing.
Contributing to this repo requires Node.js >= 22 and pnpm — pnpm itself needs Node 22.13+, and regenerating the @neon/sdk types needs Node 22.18+. The published packages support Node.js >= 20.19 at runtime (see each package's README and CONTRIBUTING.md). From the repo root:
pnpm install # install all workspaces
pnpm build # build every package (tsc + tsdown)
pnpm test:ci # run the test suites (Vitest)
pnpm lint:ci # lint + format check (Biome)
Scope a command to a single package with a filter, e.g.:
pnpm --filter @neon/env build
pnpm --filter @neon/env test:ci
Versioning is driven by Changesets. Add a changeset describing your change (pnpm changeset), and a maintainer applies the version bumps + changelogs (pnpm changeset version) on a release PR. Publishing to npm runs from a separate workflow once that PR lands on main.
Every package in this repository is licensed under Apache-2.0.
Agent tools for the Neon SDK ergonomic client, compatible with MCP, Eve, and Mastra.
{ "mcpServers": { "neon-tools": { "command": "npx", "args": [ "-y", "@neon/[email protected]" ] } }}टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
@neon/tools stdio पर लोकल चलता है।
पिछली जाँच 2026-11-14 को हुई। Agent tools for the Neon SDK ergonomic client, compatible with MCP, Eve, and Mastra.