Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Neon Auth (BYOK) icon

Neon Auth (BYOK)

Read the Neon Auth setup of your Neon branches: provider integration, trusted domains, OAuth providers, email and password rules, plugins, webhooks and OAuth clients with your own Neon API key

Unify Dynamics LLC

Tools11read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderNeon Authunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Is Neon Auth enabled on my branch and which provider does it use?
Tools called
get_branch_auth
Which branches of my Neon project have Neon Auth set up?
Tools called
list_auth_integrations
Which domains are trusted for Neon Auth on my branch?
Tools called
list_trusted_domains
Which redirect domains are whitelisted for Neon Auth in my project?
Tools called
list_redirect_domains
Which social logins are enabled for Neon Auth on my branch?
Tools called
list_oauth_providers
Does Neon Auth on my branch require email verification?
Tools called
get_email_password_config

About

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.

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.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

11 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data11 tools
  • Get branch authShow the Neon Auth integration of one branch: auth provider, database name, owner, transfer status, base URL, JWKS URL and creation time.
  • List auth integrationsList the Neon Auth integrations across the branches of a project with provider, branch, owner, base URL and JWKS URL.
  • List trusted domainsList the domains a branch trusts for Neon Auth redirects, with the auth provider each belongs to.
  • List redirect domainsList the redirect URI allow-list domains configured at project level for Neon Auth, with the auth provider each belongs to.
  • List oauth providersList the social login providers (Google, GitHub, Microsoft, Vercel) configured on a branch with type (own credentials or shared) and client id.
  • Get email password configShow the email and password sign-in rules of a branch: enabled flag, verification method, verification requirements and whether sign-up is disabled.
  • Get allow localhostShow whether Neon Auth on a branch accepts localhost redirect URLs.
  • Get auth pluginsShow the Neon Auth plugin settings of a branch: organizations (limits), magic link, phone number and OAuth provider plugin flags, and localhost…
  • Get phone number pluginShow the phone number sign-in plugin of a branch: whether it is enabled and the one-time code lifetime in seconds.
  • Get webhook configShow the Neon Auth webhook settings of a branch: enabled flag, subscribed events and timeout in seconds.
  • List oauth clientsList the OAuth clients registered with Neon Auth as an OAuth provider: client id, name, type, redirect URIs, consent skip, disabled flag and…

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-neon-auth.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

More like this

More in Other

ShipBob (BYOK)

Read your ShipBob orders, products, inventory items, returns, receiving orders, locations, channels and invoices with your own personal access token

Live · MCP + REST9 tools

Sendcloud (BYOK)

Read your Sendcloud orders, shipments, parcel tracking, returns, integrations, invoices, brands and sender addresses with your own API keys

Live · MCP + REST10 tools

Mailjet (BYOK)

Read your Mailjet contacts, contact lists, campaigns, campaign statistics, messages, senders and templates with your own API key and secret

Live · MCP + REST9 tools

GetResponse (BYOK)

Read your GetResponse account, contact lists, contacts, newsletters, autoresponders, tags and newsletter statistics with your own API key

Live · MCP + REST10 tools

Iterable (BYOK)

Read your Iterable campaigns, journeys, lists, templates, channels, message types, catalogs and users with your own API key (US data center)

Live · MCP + REST10 tools

Omnisend (BYOK)

Read your Omnisend brand, contacts, campaigns, automations, segments and products with your own API key

Live · MCP + REST9 tools

Get Neon Auth (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Neon Auth API key. Create one at https://console.neon.tech/app/settings/api-keys, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Neon Auth. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Neon Auth.