---
title: "Neon integration for LuumenAI"
url: "https://www.luumen.ai/integrations/neon/"
entity: SoftwareIntegration
category: "Databases & data platforms"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# Neon integration for LuumenAI

Inspect Neon projects and branches, then make database changes as approved steps.

## What LuumenAI can do with Neon

LuumenAI connects to Neon with an API token and exposes 107 tools (48 read-only · 39 write · 20 destructive). Reads answer immediately; writes are shown as a plan and require approval by default, configurable per tool by an administrator.

## Key facts

- Authentication: API token
- Tools available: 107 tools (48 read-only · 39 write · 20 destructive)
- Plan: available on all plans
- Category: Databases & data platforms

## About Neon with LuumenAI

Connect Neon and your agent can read the shape of your serverless Postgres estate: project settings, branch counts, the databases on a given branch, organization members, and backup schedules. When something needs to change — a new database on a branch, a new role, a revoked key — the agent shows the plan first and waits for your approval. Authentication is by API key.

## Example tools

Read-only (48 in total):

- `NEON_ACCESS_PROJECT_DETAILS_BY_ID` — Retrieves detailed information about a specific Neon serverless Postgres project.
- `NEON_COUNT_PROJECT_BRANCHES` — Get the total number of branches in a Neon project.
- `NEON_FETCH_DATABASE_FOR_BRANCH` — Retrieves a list of databases associated with a specific project and branch in the Neon platform.
- `NEON_FETCH_ORGANIZATION_MEMBERS_BY_ID` — Retrieves a list of all members associated with a specific organization in the Neon B2B SaaS integration platform.
- `NEON_FETCH_VPCENDPOINT_DETAILS_BY_ID` — Retrieves the current state and configuration details of a specific VPC endpoint assigned to a Neon organization.
- `NEON_GET_AUTH` — Retrieves authentication information about the current API request credentials.
- `NEON_GET_AUTH_ALLOW_LOCALHOST` — Retrieves the allow localhost configuration for a specific branch in a Neon project.
- `NEON_GET_AUTH_EMAIL_PROVIDER` — Retrieves the email provider configuration for Neon Auth on a specific branch.

Write and destructive (59 in total, approval required by default):

- `NEON_ACCEPT_PROJECTS_TRANSFER_REQUESTS` — Accept a transfer request for a Neon project.
- `NEON_ADD_NEW_JWKS_TO_PROJECT_ENDPOINT` — Adds a new JSON Web Key Set (JWKS) URL to a Neon project for JWT-based authentication.
- `NEON_ADD_PROJECT_EMAIL_PERMISSION` — Adds permissions for a specified email address to a particular project within the Neon B2B SaaS integration platform.
- `NEON_ADD_ROLE_TO_BRANCH` — Creates a new PostgreSQL role within a specific branch of a Neon project.
- `NEON_CREATE_API_KEY_FOR_ORGANIZATION` — Creates a new API key for the specified organization in Neon.
- `NEON_CREATE_AUTH_KEYS` — Generate SDK or API keys for authentication providers.
- `NEON_CREATE_AUTH_USER` — Create a new user in Neon Auth for a specific project branch.
- `NEON_CREATE_BRANCH_DATABASE` — Creates a new database within a specified project and branch in the Neon platform.

## Frequently asked questions

### How does LuumenAI connect to Neon?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in Neon on its own?

Read actions answer immediately. Anything that writes is shown as a plan and requires approval by default, including the 20 actions classified as destructive. Administrators configure that per tool.

### Is there an audit trail?

Every call to Neon — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/neon/