An AI coworker for Neon, in Slack.

What Doozy can do in Neon

Doozy reads your Neon projects, runs queries and manages branches. Turn off the tools that change data unless you want it to. Tools Neon marks as destructive start off. Neon's own server provides the tools, so what Doozy can do there is what Neon offers and grows as they add to it. Each tool has a switch in Doozy.

• List projects, branches and databases
• Read tables and their columns, and compare schemas between branches
• Run SQL queries and get the rows back as text
• Create branches, and try schema changes on a temporary branch
• Read logs and run database diagnostics
• Search Neon's docs

Things people ask

In a thread, after @Doozy. It answers in that thread, with what it did.

• You

  @Doozy how many orders came in last week, by day? Chart it.

• You

  @Doozy what columns does the `subscriptions` table have, and what's indexed?

• You

  @Doozy make a branch off main called `try-discounts` and add a `discount_code` column there.

• You

  @Doozy every Monday at 9, post last week's signups from the `users` table.

How to connect Neon

No keys to paste: Neon asks you to approve Doozy, the way it does for any app, and you can revoke that there any time.

1. 1

   Add Doozy to your Slack and open the Integrations page in the web app.

2. 2

   Pick Neon and click Connect. Neon's own sign-in asks you to approve Doozy.

3. 3

   Choose which of its tools Doozy may use, and mention @Doozy in a thread.

What stays off, and what's always true

Doozy works like a teammate, so it doesn't stop to ask. You decide what it can reach.

More in Security and AI & Data Use.

Works well with

One ask often crosses tools: a Sentry error becomes a GitHub pull request and a Linear issue. Doozy uses whichever it needs.

• PostgresAsk questions of your own database, read-only, in plain words.
• SupabaseQuery databases and read project logs.
• VercelCheck deployments, builds and logs.
• GitHubRead code, issues and CI, and open pull requests from branches of its own.

Questions people ask before they connect Neon

Should I connect it to production?

Neon recommends its MCP server for development and testing, not production. Point Doozy at a branch, and switch off the tools that change data unless you want them.

Can it change my data?

Its SQL and branch tools can write. Tools Neon marks as destructive start off, and each tool has its own switch, so you can leave Doozy to reads.

Can Doozy see our Neon credentials?

No. Every task runs in its own isolated workspace, and credentials stay outside it: they're added to each call on its way out. Nothing it reads or writes there can expose a key.

Will it change things in Neon without asking?

It works like a teammate, so it doesn't stop to ask, and you decide what it can reach. Tools that delete or overwrite start switched off, you can switch off any other, and every action it takes is on the audit log with who asked.

Who can connect it?

Owners and admins of your Doozy workspace. Members see what's connected and can't change it. Everyone in your Slack can ask Doozy once it's connected.

What does it cost?

Nothing extra. Every integration is included on every plan, and the 14-day trial needs no card.

Something else? Write to [email protected].