Skip to main content
Use Neon through Corsair: one client, typed API calls, optional local DB sync. Neon exposes project, branch, database, role, compute endpoint, auth, organization, and infrastructure workflows for serverless Postgres. Use Corsair permissions for destructive actions such as deleting projects, dropping branches or databases, revoking API keys, or removing VPC endpoints. What you get:
  • 110 typed API operations
  • 8 database entities synced for fast .search() / .list() queries

Setup

1

Install

2

Add the plugin

corsair.ts
3

Get credentials

Follow Get Credentials if you need help getting keys.
4

Store credentials

Use the key names documented in Get Credentials (for example api_key=, bot_token=, or OAuth client fields).

Authentication

Each tab shows how to register the plugin for that authentication method. The default authType from the plugin does not need to appear in the factory call.
corsair.ts
Store credentials with pnpm corsair setup --plugin=neon (see Get Credentials for field names). For OAuth, you typically store integration keys at the provider level and tokens per account or tenant.More: API Key

Query synced data

Synced entities support corsair.neon.db.<entity>.search() and .list(). See Database for filters and operators.

Example API calls

Read-style (read): apiKeys.listApiKeys
Write-style (write): apiKeys.createApiKey
See the full list on the API page. Use pnpm corsair list --plugin=neon and pnpm corsair schema <path> locally to inspect schemas.

Hooks

Use hooks on API calls and webhookHooks on incoming events to add logging, approvals, or side effects. See Hooks and Webhooks for routing and payload patterns.

Reference

TopicLink
APIAPI
DatabaseDatabase
CredentialsGet credentials