Connect Neon to Fondoo
Live2 min readUpdated
Create a Neon API key for the account in the Neon console. Set an org-... ID only for organization-owned projects. connectionuri.get reveals a database password, so it needs owner approval.
Official documentation: https://api-docs.neon.tech/reference/getting-started-with-neon-api
Credentials
apiKey: secret Neon API key, 20-200 characters; created in the Neon console (UNCERTAIN: menu path).orgId: optional publicorg-...organization ID; filters project listing and sets the org for new projects.
Permissions
- test() makes one cheap project read; untested capabilities stay unknown, never granted.
Capabilities
Run via connector_action over REST/MCP after add_connection_key and test_connection. Money and destructive actions need owner approval.
- Read:
projects.list,projects.get,branches.list - Money (approval):
projects.create,branches.create - Destructive (approval):
projects.delete,branches.delete,connection_uri.get
Webhooks
None: Neon has no public webhook API (UNCERTAIN).
Limits and uncertainties
- Rate: 700 requests/min with 40 rps bursts per route (UNCERTAIN); Retry-After remains authoritative.
- UNCERTAIN: console menu path, org-... format, endpoint paths and query names, and the absence of webhooks.
