# Faster Lakebase Search setup, Neon CLI updates, and a Neon MCP Claude connector

## Faster Lakebase Search setup

[Lakebase Search](/guides/postgres-ai-lakebase-search) is now easier to install. You can install both Lakebase Search extensions (`lakebase_vector` and `lakebase_text`) directly with the following `CREATE EXTENSION` statements from your SQL client or the [Neon SQL Editor](/guides/postgres-get-started-query-with-neon-sql-editor):

```sql
CREATE EXTENSION IF NOT EXISTS lakebase_vector CASCADE;
CREATE EXTENSION IF NOT EXISTS lakebase_text CASCADE;
```

Previously, you had to run an SQL statement first to load the supporting libraries.

We also updated both extensions to newer versions (`lakebase_vector` 1.0.1 and `lakebase_text` 0.1.1). If you already have them installed, see [Update an extension](/guides/postgres-extensions-pg-extensions#update-an-extension-version) to get the latest version.

**Note: Get started with Lakebase Search**

Lakebase Search is a pgvector-compatible alternative for vector, keyword, and hybrid search that scales past a billion vectors, builds indexes 50–100x faster than HNSW, and stays ready after a scale-to-zero cold start. Follow the [getting started guide](/guides/postgres-ai-lakebase-search-get-started) to enable the extensions, load sample data, and run your first vector and keyword searches.

## Postgres minor version updates

We updated supported Postgres versions to [14.24](https://www.postgresql.org/docs/release/14.24/), [15.19](https://www.postgresql.org/docs/release/15.19/), [16.15](https://www.postgresql.org/docs/release/16.15/), [17.11](https://www.postgresql.org/docs/release/17.11/), and [18.6](https://www.postgresql.org/docs/release/18.6/). Minor releases bring you the latest upstream Postgres fixes and security patches.

When a new minor version is available, Neon applies it the next time your compute restarts. For more about how we handle PostgreSQL minor version updates, refer to our [Postgres version support policy](/guides/postgres-postgresql-postgres-version-support).

## Neon CLI updates

**Store credentials in your OS keyring.** You can now keep a profile's credential in your operating system's keyring instead of a file. Pass `--keyring` to `neon auth` or `neon profile create`:

```bash
neon auth --keyring
```

The secret is stored in the macOS Keychain, Windows Credential Manager, or Linux Secret Service.

**Inspect every database at once.** `neon inspect db` now inspects every database on the branch when you omit the database name, adding a `database` column to the output. Pass the database name to inspect a single database, which also scopes `locks` and `long-running-queries` so their names resolve correctly.

**Note:** This change is also available in the Neon MCP server's `inspect_database` tool.

## Neon MCP server now an official Claude connector

The [Neon MCP server](/guides/postgres-ai-neon-mcp-server#claude-connector) is now listed in Claude's connectors. You can manage Neon from Claude: create projects and branches, run SQL, change schemas, and diagnose a slow query.

In Claude.ai or Claude Desktop, go to **Settings > Connectors**, click **Browse connectors**, add **Neon**, and authorize access to your Neon account.

<img src="../img/site-assets/neon.com/docs/changelog/claude_neon_connector.png" alt="Neon connector in Claude">

## Install Neon Agent Skills with Pi

You can now install [Neon Agent Skills](/guides/ai-agents-on-neon-ai-agent-skills) with [Pi](https://pi.dev), straight from the repository:

```bash
pi install git:github.com/neondatabase/agent-skills
```

Pi reads the skills directly, so there's no separate sync step. This joins the [existing install channels](/guides/ai-agents-on-neon-ai-agent-skills#install), including `npx skills`, the Cursor, Claude Code, Codex, and Kimi Code plugins, and `neon init`.

## New Neon Functions guides

Two new guides show what you can build on [Neon Functions](/guides/neon-functions-index), which run alongside your database as part of the [Neon backend](/guides/neon-docs-get-started-backend-overview):

- [Automate Neon Functions deployments with GitHub Actions](https://neon.com/guides/neon-functions-github-actions): set up CI/CD to deploy to production on merge and create preview functions for pull requests.
- [Monitor Neon Functions with Sentry](https://neon.com/guides/sentry-neon-functions): add error tracking, structured logs, and request tracing.

> **Try the Neon backend**
>
> Object Storage, Functions, and AI Gateway branch with your Postgres database, so your whole stack forks together.
>
> [Get started](/guides/neon-docs-get-started-backend-overview)

## Related pages

- [Add users and authentication](./auth-index.md)
- [AI tools for Agents](./ai-agents-on-neon-index.md)
- [APIs & SDKs](./apis-sdks-index.md)
- [Changelog](../changelog.md)
- [Explore the full platform: functions, object storage, AI Gateway, and more](./neon-docs-index.md)
- [Integrating with Neon](./building-on-neon-index.md)
- [Lakebase Postgres](./postgres-index.md)
- [More](./more-index.md)
- [Neon AI Gateway](./ai-gateway-index.md)
- [Neon community](./community-index.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.