# Neon AI integration on Definable

> Postgres, on a serverless platform designed to help you build reliable and scalable applications faster

## What this connects

Postgres, on a serverless platform designed to help you build reliable and scalable applications faster

Vendor: https://neon.tech/

## Tools available

**110** tools available. First 12:

- `NEON_ACCEPT_PROJECTS_TRANSFER_REQUESTS` — Accept project transfer request — Tool to accept a transfer request for a Neon project. Use when you need to accept an existing transfer request to transfer a project to your account or a specific organization.
- `NEON_ACCESS_PROJECT_DETAILS_BY_ID` — Access project details by id — Retrieves detailed information about a specific Neon serverless Postgres project. Returns comprehensive project data including configuration, database settings, compute resources, owner information, and consumption metrics. Use this action when you need to: - Get project configuration details (region, PostgreSQL version, settings) - Check project ownership and organization membership - Review compute and storage consumption metrics - Verify project settings before making updates The action is read-only and safe to call frequently. For listing multiple projects, use the retrieve_projects_list action instead.
- `NEON_ADD_NEW_JWKS_TO_PROJECT_ENDPOINT` — Add new jwks to project endpoint — Adds a new JSON Web Key Set (JWKS) URL to a Neon project for JWT-based authentication. The JWKS URL must point to a valid HTTPS endpoint that returns cryptographic keys used to verify JSON Web Tokens (JWTs). Use this action to configure authentication with identity providers like Google, Microsoft, Apple, Auth0, Clerk, or Stytch. The JWKS can be scoped to specific branches and mapped to database roles. Maximum of 10 role names can be associated with each JWKS configuration.
- `NEON_ADD_PROJECT_EMAIL_PERMISSION` — Add project email permission — Adds permissions for a specified email address to a particular project within the Neon B2B SaaS integration platform. This endpoint is used to grant access or specific rights to users for a given project, enabling collaboration and controlled resource sharing. It should be called when you need to add a new user to a project or modify existing user permissions. The endpoint associates the provided email with the specified project, likely setting up default or predefined permission levels. Note that this endpoint only adds permissions and does not provide information about existing permissions or remove them.
- `NEON_ADD_ROLE_TO_BRANCH` — Add role to branch — Creates a new PostgreSQL role within a specific branch of a Neon project. Neon is a serverless PostgreSQL platform where roles are database-level users that can connect to the database and have specific permissions. Use this endpoint to: - Create application service accounts for database access - Set up read-only users for reporting - Create admin roles for database management The created role will have an auto-generated password returned in the response. Store this password securely as it may not be retrievable later. You can use the 'reveal_role_password' endpoint to retrieve it again if needed. Note: Role names must be valid PostgreSQL identifiers (max 63 bytes).
- `NEON_COUNT_PROJECT_BRANCHES` — Count project branches — Tool to get the total number of branches in a Neon project. Use when you need to count branches without retrieving full branch details. Optionally filter by branch name using the search parameter.
- `NEON_CREATE_API_KEY_FOR_ORGANIZATION` — Create API Key for Organization — Creates a new API key for the specified organization in Neon. The API key is used for authenticating and authorizing access to the Neon API. The `key_name` parameter allows for easy identification and management of multiple API keys within the organization. IMPORTANT: The actual API key value is returned only once in the response and cannot be retrieved later. Store it securely immediately after creation. Organization API keys provide admin-level access to all organization resources, including projects, members, and settings. Only organization admins can create these keys.
- `NEON_CREATE_AUTH_KEYS` — Create Auth Provider SDK Keys — Tool to generate SDK or API keys for authentication providers. Use when setting up authentication for a Neon project with providers like Stack Auth, Better Auth, or for testing with mock provider.
- `NEON_CREATE_AUTH_USER` — Create auth user — Tool to create a new user in Neon Auth for a specific project branch. Use when you need to add authentication users to a branch that has Neon Auth enabled with the 'stack' provider. The branch must already have Neon Auth configured before creating users.
- `NEON_CREATE_BRANCH_DATABASE` — Create branch database — Creates a new database within a specified project and branch in the Neon platform. This endpoint allows users to set up a new database with a custom name and assign an owner role, facilitating the organization and management of databases within the Neon ecosystem. It should be used when initializing a new database for a specific project or when branching requires a separate database instance. The endpoint is particularly useful for developers and database administrators who need to quickly set up new databases as part of their workflow or application deployment process. Note that this operation only creates the database; additional steps may be required to configure specific schemas, tables, or access permissions within the newly created database.
- `NEON_CREATE_BRANCHES_AUTH` — Enable Neon Auth for branch — Tool to enable Neon Auth integration for a branch. Use when you need to set up authentication for a specific branch in a Neon project.
- `NEON_CREATE_BRANCHES_DATA_API` — Create Neon Data API — Creates a new instance of Neon Data API in the specified branch. The Data API provides a RESTful interface to query your Postgres database using HTTP requests. Use this action when you need to expose database access via REST API endpoints with JWT-based authentication.

## Auth

Auth schemes: `API_KEY`.

## How agents use Neon

Inside a Definable workflow, Neon is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Neon** — the Researcher (GPT-5.5) pulls context from Neon (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Neon** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Neon (create record, post message, draft email).
- **Designer / Engineer → Distributor → Neon** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Neon (attach file, open PR comment, post status).

The Verifier checks every Neon call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- databases — https://definable.ai/apps/category/databases/
- developer tools — https://definable.ai/apps/category/developer-tools/

## Related

- HTML page: https://definable.ai/apps/neon/
- Same category (databases): https://definable.ai/apps/category/databases/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt