Neon is serverless Postgres with branching and scale-to-zero pricing. Connecting Neon to clariBI brings your branch databases into your AI analyses through safe read-only SQL.
Why connect Neon
Branch databases make it cheap to keep many environments separate. Reporting against them usually requires juggling connection strings.
With Neon connected, you point clariBI at a specific branch and ask questions in natural language; the AI engine writes and runs the SELECT for you.
How the connection works
clariBI talks to Neon through its hosted MCP server at https://mcp.neon.tech/mcp. Authentication uses an OAuth flow that clariBI registers itself for (no developer console setup on your side). Tokens stay encrypted server-side and never leave clariBI in clear form.
sequenceDiagram
actor U as You
participant C as clariBI
participant V as Neon
U->>C: Click Authorize with Neon
C->>V: Open OAuth authorization
V-->>U: Grant read access?
U->>V: Approve
V-->>C: Authorization code
C->>V: Exchange code for tokens
V-->>C: Access + refresh tokens
C->>C: Encrypt and store credentials
C-->>U: Connection ready
Available tools
clariBI exposes the read-only Neon tools that the vendor's MCP server publishes at connection time. Write operations (create, update, delete, send, refund) are filtered out by a name-pattern blocklist before any tool reaches the analysis engine, so connecting Neon cannot modify data on the vendor side.
The exact tool inventory depends on the Neon features your account has access to. After connecting, try a few natural-language questions to see what Neon data clariBI can pull.
Data flow during analysis
When you ask a question that maps to Neon, the AI engine routes to the right tool, reads the result, and pairs the answer with a chart you can pin to a dashboard.
sequenceDiagram
actor U as You
participant C as clariBI
participant AI as AI engine
participant V as Neon
U->>C: Ask a question about application database
C->>AI: Plan the analysis
AI->>V: Call the right tool
V-->>AI: Tool result
AI->>AI: Summarize and chart
C-->>U: Answer plus visual
Setting up the connection
- Open Data Sources in the clariBI sidebar.
- Click Add data source.
- Open the MCP Servers tab.
- Click the Neon card.
- Click Authorize with Neon.
- Sign in to Neon in the popup window and grant the requested read scopes.
- Back in clariBI, give your data source a name.
- Click Finish.
Permissions and data access
clariBI requests Neon projects:read scope. No data can be modified and no schema changes are possible. Disconnect from your Neon Console or from clariBI Settings.
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
| "Branch not found" | A referenced branch was deleted or renamed in Neon. | Refresh the branch list in clariBI by re-running the analysis. |