Skip to main content
Agent skill

Neon Automation

Automate Neon serverless Postgres operations -- manage projects, branches, databases, roles, and connection URIs via the Composio MCP integration.

Get started

Get the complete skill folder, including its scripts and reference files.

This workflow depends on an external MCP integration. Check the source for the server, account access and setup it requires.

When to use this skill

Use Neon Automation when an AI agent needs a reusable SKILL.md workflow for this job: Automate Neon serverless Postgres operations -- manage projects, branches, databases, roles, and connection URIs via the Composio MCP integration.

When not to use it

Skip Neon Automation when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/neon-automation
# Save SKILL.md to ~/.claude/skills/neon-automation/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/neon-automation/SKILL.md. For a shared project, commit the folder at .claude/skills/neon-automation/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Neon Automation skill for this task: Use Neon Automation when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
75/100
Practical detail
68/100
Source evidence
63/100
Source signals
80/100
Model compatibility evidence
  • claudeinferred

    The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# 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](https://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

| Pitfall | Detail | |---------|--------| | org_id required | `NEON_RETRIEVE_PROJECTS_LIST` returns HTTP 400 "org_id is required" when using a personal API key. Call `NEON_GET_USER_ORGANIZATIONS` first. | | Incomplete pagination | Project lists may be incomplete without pagination. Iterate using `cursor` until it is empty. | | Rate limiting | `NEON_RETRIEVE_PROJECTS_LIST` returns HTTP 429 on bursty listing. Avoid redundant calls and back off before retrying. | | Invalid role/database pairing | `NEON_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 secret | The returned URI includes credentials. Never log, display, or share it in plain text. |

---

## Quick Reference

| Tool Slug | Description | |-----------|-------------| | `NEON_RETRIEVE_PROJECTS_LIST` | List all Neon projects with pagination and search | | `NEON_ACCESS_PROJECT_DETAILS_BY_ID` | Get project configuration and consumption metrics | | `NEON_GET_BRANCHES_FOR_PROJECT` | List branches within a project | | `NEON_FETCH_DATABASE_FOR_BRANCH` | List databases on a specific branch | | `NEON_GET_PROJECT_CONNECTION_URI` | Get a Postgres connection URI (with credentials) | | `NEON_RETRIEVE_BRANCH_DATABASE_DETAILS` | Inspect database metadata and settings | | `NEON_GET_USER_ORGANIZATIONS` | List organizations for the authenticated user | | `NEON_CREATE_API_KEY_FOR_ORGANIZATION` | Create a new API key for an organization | | `NEON_GET_BRANCH_ROLES_FOR_PROJECT` | List roles available on a branch |

---

*Powered by [Composio](https://composio.dev)*

Intended uses

  • Use Neon Automation when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.