Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Neon Auth (BYOK) — connector documentation

  • MCP endpoint: https://byok-neon-auth.connectorbay.com/mcp
  • REST API: POST https://byok-neon-auth.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-neon-auth.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Neon Auth API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-neon-auth.connectorbay.com/health · Tool schemas: https://byok-neon-auth.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-neon-auth · agent@connectorbay.com

What Neon Auth (BYOK) is for

Neon Auth (BYOK) lets an AI assistant read your own Neon Auth data through the Neon Auth API with a key you supply (API key). Read-only: 11 tools (get_branch_auth, list_auth_integrations, list_trusted_domains, list_redirect_domains, list_oauth_providers, get_email_password_config, get_allow_localhost, get_auth_plugins, get_phone_number_plugin, get_webhook_config, list_oauth_clients). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to console.neon.tech. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Neon Auth. Neon Auth and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Is Neon Auth enabled on my branch and which provider does it use?"
  • "Which branches of my Neon project have Neon Auth set up?"
  • "Which domains are trusted for Neon Auth on my branch?"
  • "Which redirect domains are whitelisted for Neon Auth in my project?"
  • "Which social logins are enabled for Neon Auth on my branch?"
  • "Does Neon Auth on my branch require email verification?"

What it does

  • get_branch_auth: Show the Neon Auth integration of one branch: auth provider, database name, owner, transfer status, base URL, JWKS URL and creation time.
  • list_auth_integrations: List the Neon Auth integrations across the branches of a project with provider, branch, owner, base URL and JWKS URL.
  • list_trusted_domains: List the domains a branch trusts for Neon Auth redirects, with the auth provider each belongs to.
  • list_redirect_domains: List the redirect URI allow-list domains configured at project level for Neon Auth, with the auth provider each belongs to.
  • list_oauth_providers: List the social login providers (Google, GitHub, Microsoft, Vercel) configured on a branch with type (own credentials or shared) and client id. Client secrets are not picked.
  • get_email_password_config: Show the email and password sign-in rules of a branch: enabled flag, verification method, verification requirements and whether sign-up is disabled.
  • get_allow_localhost: Show whether Neon Auth on a branch accepts localhost redirect URLs.
  • get_auth_plugins: Show the Neon Auth plugin settings of a branch: organizations (limits), magic link, phone number and OAuth provider plugin flags, and localhost access. Mail server credentials are not picked.
  • get_phone_number_plugin: Show the phone number sign-in plugin of a branch: whether it is enabled and the one-time code lifetime in seconds.
  • get_webhook_config: Show the Neon Auth webhook settings of a branch: enabled flag, subscribed events and timeout in seconds. The webhook URL is not picked.
  • list_oauth_clients: List the OAuth clients registered with Neon Auth as an OAuth provider: client id, name, type, redirect URIs, consent skip, disabled flag and creation time.

BYOK key

You bring your own Neon Auth API key (https://console.neon.tech/app/settings/api-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to console.neon.tech over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Neon Auth API (console.neon.tech) with a BYOK key; documentation: https://neon.com/docs/reference/api-reference. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Neon Auth. Neon Auth and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Neon Auth account.

Built for: Worldwide. Languages: English.