Update to Neon

{
  "canonical_app_id": "asdk_app_69e0086d87088191a3edc052fa50c29f",
  "connector_id": "asdk_app_69e0086d87088191a3edc052fa50c29f",
  "created_at": "2026-05-26T19:35:17.821010Z",
  "discoverability": "LISTED",
  "id": "plugin_asdk_app_69e0086d87088191a3edc052fa50c29f",
  "is_template": false,
  "name": "neon-postgres",
  "release": {
    "app_ids": [],
    "app_manifest": {
      "apps": {
        "neon": {
          "id": "asdk_app_69e0086d87088191a3edc052fa50c29f",
          "required": true
        }
      }
    },
    "app_templates": [],
    "description": "Manage your Neon backend with the Neon agent skills and the Neon MCP Server: Lakebase Postgres, branching, Object Storage, Functions, and the AI Gateway",
    "display_name": "Neon",
    "id": "pluginrel_3d909d4d2dc48191a6de546c9f10c32b",
    "interface": {
      "brand_color": null,
      "capabilities": [
        "Read",
        "Write"
      ],
      "category": "Developer Tools",
      "composer_icon_dark_url": "https://files.openai.com/content?id=file_00000000b1a881f5a7a8c358a1fcee36",
      "composer_icon_url": "https://files.openai.com/content?id=file_00000000768081f98d4a28dfe71cff47",
      "default_prompt": "Create a Neon database and add Neon Auth to my application.",
      "default_prompts": [
        "Create a Neon database and add Neon Auth to my application.",
        "Deploy a Neon Function that uses Neon Object Storage.",
        "Add AI to my application with the Neon AI Gateway."
      ],
      "developer_name": "Neon (A Databricks, Inc. company)",
      "logo_url": "https://files.openai.com/content?id=file_000000007a2c81f689ae4f30d1c7ed08",
      "logo_url_dark": "https://files.openai.com/content?id=file_00000000076081f59170053f0004d812",
      "long_description": "Manage Neon projects directly through ChatGPT. Run SQL and transactions on Lakebase Postgres, inspect and diff table schemas, apply migrations on a temporary branch before committing them, and provision Auth and the Data API. Create copy-on-write branches for isolated work, query logs from Serverless Functions and Object Storage for debugging, tune slow queries, and search Neon docs all through natural language commands. Connect with OAuth. During authorization, choose read-only or full access. Always review and authorize actions before execution.",
      "plugin_category_id": "developer tools",
      "privacy_policy_url": "https://neon.com/privacy-policy",
      "screenshot_urls": [],
      "short_description": "Manage your Neon backend",
      "terms_of_service_url": "https://neon.com/platform-terms",
      "website_url": "https://neon.com"
    },
    "keywords": [
      "neon",
      "lakebase",
      "postgres",
      "serverless",
      "database",
      "mcp"
    ],
    "mcp_servers": [
      {
        "key": "neon",
        "metadata": {
          "headers": {},
          "type": "streamable-http",
          "url": "https://mcp.neon.tech/mcp"
        }
      }
    ],
    "onboarding_skill_name": null,
    "requires_local_executor": true,
    "skills": [
      {
        "description": "Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, and the AI Gateway. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when \"Neon\" or \"Lakebase Postgres\" is mentioned. Child skill neon-postgres wins for an existing DATABASE_URL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "neon",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "bolt",
          "short_description": "Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, and the AI Gateway. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when \"Neon\" or \"Lakebase Postgres\" is mentioned. Child skill neon-postgres wins for an existing DATABASE_URL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database."
        },
        "name": "neon",
        "plugin_release_skill_id": "pluginrsk_6abe81564c3c819186f41b0e49b21048"
      },
      {
        "description": "One API and one credential for frontier and open-source LLMs, built into your Neon branch and powered by Databricks. Use when a user wants to call an LLM, add AI/chat/an agent to their app, route between model providers (OpenAI, Anthropic, Google/Gemini, Meta, Alibaba, and more), or avoid juggling separate provider API keys and accounts — especially when they already use Neon and want AI requests to branch with their project. Works with the OpenAI SDK, Anthropic SDK, google-genai, the Vercel AI SDK, and Mastra by changing only the base URL. Triggers include \"call an LLM\", \"add AI to my app\", \"chat completion\", \"model routing\", \"LLM proxy/gateway\", \"one API for all models\", \"use Claude/GPT/Gemini\", \"AI SDK\", \"Mastra agent\", \"Neon AI Gateway\", and \"log/rate-limit AI calls\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "neon-ai-gateway",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "One API and one credential for frontier and open-source LLMs, built into your Neon branch and powered by Databricks. Use when a user wants to call an LLM, add AI/chat/an agent to their app, route between model providers (OpenAI, Anthropic, Google/Gemini, Meta, Alibaba, and more), or avoid juggling separate provider API keys and accounts — especially when they already use Neon and want AI requests to branch with their project. Works with the OpenAI SDK, Anthropic SDK, google-genai, the Vercel AI SDK, and Mastra by changing only the base URL. Triggers include \"call an LLM\", \"add AI to my app\", \"chat completion\", \"model routing\", \"LLM proxy/gateway\", \"one API for all models\", \"use Claude/GPT/Gemini\", \"AI SDK\", \"Mastra agent\", \"Neon AI Gateway\", and \"log/rate-limit AI calls\"."
        },
        "name": "neon-ai-gateway",
        "plugin_release_skill_id": "pluginrsk_6abe81579808819194fa6f21781ee872"
      },
      {
        "description": "Add authentication to a new app. Use for \"add auth\", \"add login\", Neon Auth (Managed Better Auth), identity routing, sign-up, sign-in, password reset, email OTP, magic links, organizations, phone OTP, OAuth, passkeys, MFA, trusted domains, invalid domain, and @neondatabase/auth. No existing identity: default to Managed Better Auth. Keep working Better Auth, Clerk, Supabase Auth, or another IdP. User asked to migrate from Supabase Auth: Managed Better Auth. A required plugin outside Managed support: self-managed Better Auth on a Neon Function or the existing app host. Also use for auth APIs in @neondatabase/neon-js.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "neon-auth",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "heart",
          "short_description": "Add authentication to a new app. Use for \"add auth\", \"add login\", Neon Auth (Managed Better Auth), identity routing, sign-up, sign-in, password reset, email OTP, magic links, organizations, phone OTP, OAuth, passkeys, MFA, trusted domains, invalid domain, and @neondatabase/auth. No existing identity: default to Managed Better Auth. Keep working Better Auth, Clerk, Supabase Auth, or another IdP. User asked to migrate from Supabase Auth: Managed Better Auth. A required plugin outside Managed support: self-managed Better Auth on a Neon Function or the existing app host. Also use for auth APIs in @neondatabase/neon-js."
        },
        "name": "neon-auth",
        "plugin_release_skill_id": "pluginrsk_6abe8157752081918681acdff24a6829"
      },
      {
        "description": "Long-running, serverless Node.js HTTP functions deployed onto your Neon branch, with DATABASE_URL injected automatically and compute that runs next to your data. Use when a user wants to host an API, an AI agent with long streaming responses, a WebSocket or server-sent-events (SSE) server, a webhook handler, a Discord bot, an MCP server, or any request/response workload that risks timing out on short, lambda-style serverless functions — and wants it to branch with their database. Also use for Function Triggers: a cron or an object-storage event that POSTs to a function. Triggers include \"serverless function\", \"deploy an API\", \"long-running function\", \"streaming agent\", \"SSE server\", \"WebSocket server\", \"webhook handler\", \"MCP server\", \"cron\", \"function trigger\", \"scheduled function\", \"cron job\", \"object storage trigger\", \"on upload\", \"run code next to my database\", \"function that won't time out\", \"function logs\", \"Neon Functions\", \"Neon Compute\", \"DDoS protection\", \"rate limiting\", and \"production hardening\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "neon-functions",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Long-running, serverless Node.js HTTP functions deployed onto your Neon branch, with DATABASE_URL injected automatically and compute that runs next to your data. Use when a user wants to host an API, an AI agent with long streaming responses, a WebSocket or server-sent-events (SSE) server, a webhook handler, a Discord bot, an MCP server, or any request/response workload that risks timing out on short, lambda-style serverless functions — and wants it to branch with their database. Also use for Function Triggers: a cron or an object-storage event that POSTs to a function. Triggers include \"serverless function\", \"deploy an API\", \"long-running function\", \"streaming agent\", \"SSE server\", \"WebSocket server\", \"webhook handler\", \"MCP server\", \"cron\", \"function trigger\", \"scheduled function\", \"cron job\", \"object storage trigger\", \"on upload\", \"run code next to my database\", \"function that won't time out\", \"function logs\", \"Neon Functions\", \"Neon Compute\", \"DDoS protection\", \"rate limiting\", and \"production hardening\"."
        },
        "name": "neon-functions",
        "plugin_release_skill_id": "pluginrsk_6abe81569fac8191b43b49800bf14a21"
      },
      {
        "description": "S3-compatible object storage that branches with your Neon project, so files and the database stay in sync across every branch. Use when a user wants object storage, a bucket, blob/file storage, or somewhere to put uploads, images, documents, avatars, or user-generated files for their app or agent — especially when they already use (or are setting up) Lakebase Postgres and don't want to add a separate storage provider like AWS S3, Cloudflare R2, or Supabase Storage. Triggers include \"object storage\", \"bucket\", \"blob storage\", \"file storage\", \"store uploads/images/files\", \"S3-compatible storage\", \"presigned URL\", \"where do I put files\", \"storage logs\", \"bucket logs\", \"CDN in front of object storage\", \"Neon Object Storage\", \"Neon Storage\", and \"storage that branches with my database\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "neon-object-storage",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "pdf",
          "short_description": "S3-compatible object storage that branches with your Neon project, so files and the database stay in sync across every branch. Use when a user wants object storage, a bucket, blob/file storage, or somewhere to put uploads, images, documents, avatars, or user-generated files for their app or agent — especially when they already use (or are setting up) Lakebase Postgres and don't want to add a separate storage provider like AWS S3, Cloudflare R2, or Supabase Storage. Triggers include \"object storage\", \"bucket\", \"blob storage\", \"file storage\", \"store uploads/images/files\", \"S3-compatible storage\", \"presigned URL\", \"where do I put files\", \"storage logs\", \"bucket logs\", \"CDN in front of object storage\", \"Neon Object Storage\", \"Neon Storage\", and \"storage that branches with my database\"."
        },
        "name": "neon-object-storage",
        "plugin_release_skill_id": "pluginrsk_6abe8158e7e08191892cbe237b9f6ea0"
      },
      {
        "description": "Guides and best practices for working with Lakebase Postgres on Neon: connections, pooled vs direct, schema migrations, branching, autoscaling, scale-to-zero, instant restore, read replicas, IP allow lists, logical replication, and Lakebase Search. Use when the work is an existing DATABASE_URL, SQL, schema, inspect, or search. New backends, Auth, files, Functions, and LLM calls go to the parent `neon` skill. Also use for \"@neondatabase/serverless\", \"@neondatabase/neon-js\", \"neon inspect db\", \"semantic search\", \"vector search\", \"full-text search\", \"BM25\", or \"hybrid search\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "neon-postgres",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Guides and best practices for working with Lakebase Postgres on Neon: connections, pooled vs direct, schema migrations, branching, autoscaling, scale-to-zero, instant restore, read replicas, IP allow lists, logical replication, and Lakebase Search. Use when the work is an existing DATABASE_URL, SQL, schema, inspect, or search. New backends, Auth, files, Functions, and LLM calls go to the parent `neon` skill. Also use for \"@neondatabase/serverless\", \"@neondatabase/neon-js\", \"neon inspect db\", \"semantic search\", \"vector search\", \"full-text search\", \"BM25\", or \"hybrid search\"."
        },
        "name": "neon-postgres",
        "plugin_release_skill_id": "pluginrsk_6abe81580014819194c8afc4d37a3201"
      },
      {
        "description": "Choose and create the right Neon branch type for testing and development. Use when users ask about Neon branching, migration testing with real data, isolated test environments, schema-only branch workflows for sensitive data, resetting a branch from its parent, branch expiration and CI/CD branch lifecycles, or branch creation via Neon CLI or Neon MCP. Triggers include \"Neon branch\", \"test migrations safely\", \"branch production data\", \"schema-only branch\", \"reset branch\", \"branch per PR\" and \"sensitive data testing\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "neon-postgres-branches",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "hierarchy",
          "short_description": "Choose and create the right Neon branch type for testing and development. Use when users ask about Neon branching, migration testing with real data, isolated test environments, schema-only branch workflows for sensitive data, resetting a branch from its parent, branch expiration and CI/CD branch lifecycles, or branch creation via Neon CLI or Neon MCP. Triggers include \"Neon branch\", \"test migrations safely\", \"branch production data\", \"schema-only branch\", \"reset branch\", \"branch per PR\" and \"sensitive data testing\"."
        },
        "name": "neon-postgres-branches",
        "plugin_release_skill_id": "pluginrsk_6abe8157da9881919c8d97ef8812b5fb"
      },
      {
        "description": "Diagnose and fix excessive Postgres egress (network data transfer) in a codebase. Use when a user mentions high database bills, unexpected data transfer costs, network transfer charges, egress spikes, \"why is my Neon bill so high\", \"database costs jumped\", SELECT * optimization, query overfetching, reduce Neon costs, optimize database usage, or wants to reduce data sent from their database to their application. Also use when reviewing query patterns for cost efficiency, even if the user doesn't explicitly mention egress or data transfer.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "neon-postgres-egress-optimizer",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "chart",
          "short_description": "Diagnose and fix excessive Postgres egress (network data transfer) in a codebase. Use when a user mentions high database bills, unexpected data transfer costs, network transfer charges, egress spikes, \"why is my Neon bill so high\", \"database costs jumped\", SELECT * optimization, query overfetching, reduce Neon costs, optimize database usage, or wants to reduce data sent from their database to their application. Also use when reviewing query patterns for cost efficiency, even if the user doesn't explicitly mention egress or data transfer."
        },
        "name": "neon-postgres-egress-optimizer",
        "plugin_release_skill_id": "pluginrsk_6abe815671d881919cb04111b50d8de2"
      }
    ],
    "version": "2.1.0"
  },
  "scope": "GLOBAL",
  "share_url": "https://chatgpt.com/plugins/neon-postgres?open_in_app",
  "status": "ENABLED"
}