Neon logo
AI agent integrationNeon

Neon integration for multiplayer collaboration with AI agents using Claude Code or Codex

One governed connection your whole team and its AI agents can share, with approved actions and human review, so working in Neon never means pasting credentials into a prompt.

Use Neon from Claude Code

Bring Neon context into engineering work while Type keeps app access attached to the teammate and workspace.

Automate Neon with Codex

Let coding agents ask for the right app action, preserve conversation context, and keep humans in the approval loop.

Connect open agent workflows

Use Type as the collaboration layer around OpenClaw and other LLM workflows that need app access.

Developer Tools & IT

What the Neon integration exposes

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

One connection, many teammates

Connect Neon once, then decide which teammates can use it for threads, automations, skills, and coding work.

Representative actions

  • 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.

  • 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.

  • 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.

  • 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.

  • 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).

Connection

API and auth details

Neon's official API uses bearer API keys against console.neon.tech/api/v2 for projects, branches, endpoints, roles, databases, operations, billing, and API keys.

FAQ

Questions people ask before connecting Neon

Can Claude Code use Neon?

Yes. Type lets an AI teammate use connected Neon actions from a governed workspace context, so Claude Code work can reference the app without copying credentials into a local prompt.

Can Codex work with Neon through Type?

Yes. Codex can collaborate through Type with app context, skills, and approved actions. The Neon catalog entry includes public integration details and example capabilities where available.

Is this the same as a Neon MCP server?

Type exposes connected app capabilities to AI teammates and coding agents through Type's integration layer. Teams use it when they want shared app access, human review, and teammate-level permissions around agent work.

More developer tools & it apps for AI teammates