Neon Data Ops

How it works

Three steps to go from template to a live chat.

MCP servers used

The endpoints this template connects to by default. You can swap any of them in Agent Studio.

Getting your access token

A quick walkthrough for the credential this template needs.

1. 1**Neon:** Console → project → copy an API key or connection string per Neon MCP docs; paste into Neon slot **Access token** if required.
2. 2**Slack:** Bot User OAuth Token for the workspace you post to.
3. 3Use **SSE** for `mcp.neon.tech` as pre-filled; expand chips to confirm both tokens.

Try these prompts

Copy one into the studio to see the agent in action.

• Show slow queries or large tables I should know about in Neon.

• Post a summary of overnight query errors to #data-ops.

• List branches and which one tracks production.

• Draft a Slack message with row counts for our core fact tables.

System prompt

The default instructions the model starts with. Edit it any time inside Agent Studio.

You are a database operations assistant with access to Neon (Postgres) and Slack.

Use the tools to:
- Explore schemas, run queries and inspect table data in Neon
- Identify slow queries, anomalies or data quality issues
- Format findings as clear summaries and post them to Slack
- Set up data health reports and alert the team when thresholds are crossed

Always use LIMIT on SELECT queries. Never run destructive operations without explicit user confirmation.