Get the FREE Ultimate OpenClaw Setup Guide →

Neon Automation

Scanned
npx machina-cli add skill ComposioHQ/awesome-claude-skills/neon-automation --openclaw
Files (1)
SKILL.md
4.9 KB

Neon Automation

Automate your Neon serverless Postgres workflows -- list projects and branches, inspect databases, retrieve connection URIs, manage roles, and integrate Neon database operations into cross-app pipelines.

Toolkit docs: composio.dev/toolkits/neon


Setup

  1. Add the Composio MCP server to your client: https://rube.app/mcp
  2. Connect your Neon account when prompted (API key authentication)
  3. Start using the workflows below

Core Workflows

1. List Projects

Use NEON_RETRIEVE_PROJECTS_LIST to discover all projects associated with the authenticated user.

Tool: NEON_RETRIEVE_PROJECTS_LIST
Inputs:
  - org_id: string (REQUIRED when using a personal API key)
  - limit: integer (1-400, default 10)
  - cursor: string (pagination cursor from previous response)
  - search: string (search by project name or ID, supports partial match)
  - timeout: integer (milliseconds; returns partial results on timeout)

Important: When using a personal API key, org_id is required. Retrieve it first via NEON_GET_USER_ORGANIZATIONS.

2. Get Project Details

Use NEON_ACCESS_PROJECT_DETAILS_BY_ID to inspect project configuration, owner info, and consumption metrics.

Tool: NEON_ACCESS_PROJECT_DETAILS_BY_ID
Inputs:
  - project_id: string (required) -- format: "adjective-noun-number", e.g., "dry-smoke-26258271"

3. List Branches for a Project

Use NEON_GET_BRANCHES_FOR_PROJECT to enumerate branches (development stages) within a project.

Tool: NEON_GET_BRANCHES_FOR_PROJECT
Inputs:
  - project_id: string (required)
  - search: string (optional, search by branch name or ID)

4. List Databases on a Branch

Use NEON_FETCH_DATABASE_FOR_BRANCH to inventory databases within a specific project and branch.

Tool: NEON_FETCH_DATABASE_FOR_BRANCH
Inputs:
  - project_id: string (required)
  - branch_id: string (required)

5. Get Connection URI

Use NEON_GET_PROJECT_CONNECTION_URI to obtain a Postgres connection string for a project/branch/database.

Tool: NEON_GET_PROJECT_CONNECTION_URI
Inputs:
  - project_id: string (required)
  - database_name: string (required) -- e.g., "neondb"
  - role_name: string (required) -- e.g., "neondb_owner"
  - branch_id: string (optional, defaults to project default branch)
  - endpoint_id: string (optional, defaults to read-write endpoint)
  - pooled: boolean (optional, adds -pooler for connection pooling)

Security: The returned URI includes credentials. Treat it as a secret -- do not log or share it.

6. Inspect Database Details and Roles

Use NEON_RETRIEVE_BRANCH_DATABASE_DETAILS to verify a database before connecting, and NEON_GET_BRANCH_ROLES_FOR_PROJECT to list available roles.

Tool: NEON_RETRIEVE_BRANCH_DATABASE_DETAILS
Inputs:
  - project_id: string (required)
  - branch_id: string (required)
  - database_name: string (required)

Tool: NEON_GET_BRANCH_ROLES_FOR_PROJECT
Inputs:
  - project_id: string (required)
  - branch_id: string (required)

Known Pitfalls

PitfallDetail
org_id requiredNEON_RETRIEVE_PROJECTS_LIST returns HTTP 400 "org_id is required" when using a personal API key. Call NEON_GET_USER_ORGANIZATIONS first.
Incomplete paginationProject lists may be incomplete without pagination. Iterate using cursor until it is empty.
Rate limitingNEON_RETRIEVE_PROJECTS_LIST returns HTTP 429 on bursty listing. Avoid redundant calls and back off before retrying.
Invalid role/database pairingNEON_GET_PROJECT_CONNECTION_URI returns 401/403 when the database_name/role_name pairing is invalid. Use NEON_GET_BRANCH_ROLES_FOR_PROJECT to select an allowed role.
Connection URI is a secretThe returned URI includes credentials. Never log, display, or share it in plain text.

Quick Reference

Tool SlugDescription
NEON_RETRIEVE_PROJECTS_LISTList all Neon projects with pagination and search
NEON_ACCESS_PROJECT_DETAILS_BY_IDGet project configuration and consumption metrics
NEON_GET_BRANCHES_FOR_PROJECTList branches within a project
NEON_FETCH_DATABASE_FOR_BRANCHList databases on a specific branch
NEON_GET_PROJECT_CONNECTION_URIGet a Postgres connection URI (with credentials)
NEON_RETRIEVE_BRANCH_DATABASE_DETAILSInspect database metadata and settings
NEON_GET_USER_ORGANIZATIONSList organizations for the authenticated user
NEON_CREATE_API_KEY_FOR_ORGANIZATIONCreate a new API key for an organization
NEON_GET_BRANCH_ROLES_FOR_PROJECTList roles available on a branch

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/neon-automation/SKILL.mdView on GitHub

Overview

Neon Automation streamlines Neon serverless Postgres workflows through the Composio MCP integration. It enables listing projects and branches, inspecting databases, retrieving connection URIs, and managing roles, so Neon DB operations can be embedded in cross‑app pipelines.

How This Skill Works

It uses a suite of MCP tools (e.g., NEON_RETRIEVE_PROJECTS_LIST, NEON_GET_PROJECT_CONNECTION_URI, NEON_RETRIEVE_BRANCH_DATABASE_DETAILS) to perform common Neon tasks. After adding the MCP server and authenticating Neon with an API key, you invoke workflows with structured inputs to fetch data, then pass results into your apps or CI/CD pipelines. Security notes: connection URIs include credentials and must be treated as secrets.

When to Use It

  • When you need to enumerate all Neon projects for an authenticated user
  • When you need project details, ownership info, or consumption metrics
  • When you want to list branches within a project to support environment pipelines
  • When you need to discover databases on a specific branch
  • When you must generate a secure connection URI for a project/branch/database to connect an app

Quick Start

  1. Step 1: Add the Composio MCP server to your client: https://rube.app/mcp
  2. Step 2: Connect your Neon account when prompted (API key authentication)
  3. Step 3: Run a sample workflow such as NEON_RETRIEVE_PROJECTS_LIST or NEON_GET_PROJECT_CONNECTION_URI with the required inputs

Best Practices

  • Ensure org_id is provided if using a personal API key
  • Use cursor/pagination loops to fetch complete project lists
  • Validate role/database pair with NEON_GET_BRANCH_ROLES_FOR_PROJECT before requesting a URI
  • Treat the returned URI as a secret and limit logging and exposure
  • Leverage optional inputs (branch_id, endpoint_id, pooled) to optimize connections and security

Example Use Cases

  • Onboard a new Neon project by listing projects, fetching details, and retrieving a connection URI for deployment
  • Integrate Neon into a CI job by retrieving a project URI for test environments
  • Audit Neon usage by retrieving project details and consumption metrics
  • Prepare a multi-branch pipeline by listing branches and databases for each project
  • Validate database readiness by inspecting database details before connecting

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers