How SHAI connects to it
This one is a remote MCP server the vendor runs, and SHAI signs in to it the way the MCP specification says to: you click Connect, the vendor's own consent screen opens, and what comes back is a grant SHAI seals for this workspace alone. SHAI never sees your password, the grant is refreshed before it expires, and revoking it at the vendor's end switches it off here. A run reaches its tools through the same bridge and the same approval ladder as everything else.
What it needs
one click here, then your own sign-in at the vendor
One click on /connections, then your own sign-in at the vendor. SHAI holds the grant, never your password, and you can revoke it at the vendor at any time.
Route read from neon.com/docs/ai/neon-mcp-server (https://mcp.neon.tech/mcp) · verified 2026-09-17 · entry 73 of the integrations list
Whatever a run does with this tool goes through one door and one approval row: reading is allowed by default, anything that writes, sends or spends stops and asks first, and you can set that per tool on Connections. Plain text for this page: /integrations/neon/index.md.