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

Netlify TLS and Hooks (BYOK) — connector documentation

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

What Netlify TLS and Hooks (BYOK) is for

Netlify TLS and Hooks (BYOK) lets an AI assistant read your own Netlify TLS and Hooks data through the Netlify TLS and Hooks API with a key you supply (personal access token). Read-only: 9 tools (get_site_tls_certificate, list_site_certificates, list_build_hooks, list_notification_hooks, list_hook_types, list_site_files, list_site_assets, list_addon_services, get_addon_service). 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 api.netlify.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Netlify TLS and Hooks. Netlify TLS and Hooks 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:

  • "When does the TLS certificate of my Netlify site expire?"
  • "Which certificates exist for www.example.com on my Netlify site?"
  • "What build hooks does my Netlify site have?"
  • "Which deploy notifications are set up for my Netlify site?"
  • "What kinds of notification hooks can I add on Netlify?"
  • "Which files are published on my Netlify site?"

What it does

  • get_site_tls_certificate: Show the TLS certificate state of a Netlify site: state, covered domains, creation, update and expiry time.
  • list_site_certificates: List the TLS certificates Netlify holds for one domain of a site, with state, covered domains and expiry.
  • list_build_hooks: List the build hooks of a Netlify site with title, branch and creation time. The secret trigger URL is not returned.
  • list_notification_hooks: List the deploy notification hooks of a Netlify site with type, event, disabled flag and dates. Hook settings are not returned.
  • list_hook_types: List the notification hook types Netlify supports with the events each can react to.
  • list_site_files: List the files of the site's current deploy with path, MIME type, size and content hash.
  • list_site_assets: List the uploaded asset records of a Netlify site with name, state, content type, size and visibility. Download URLs and keys are not returned.
  • list_addon_services: Search the Netlify add-on (extension service) catalog, optionally by text, with name, slug, description, tags and environments.
  • get_addon_service: Get one Netlify add-on from the catalog by its slug: name, description, tags and environments.

BYOK key

You bring your own Netlify TLS and Hooks personal access token (https://app.netlify.com/user/applications#personal-access-tokens). 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 api.netlify.com 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 Netlify TLS and Hooks API (api.netlify.com) with a BYOK key; documentation: https://open-api.netlify.com/. 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 Netlify TLS and Hooks. Netlify TLS and Hooks 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 Netlify TLS and Hooks account.

Built for: Worldwide. Languages: English.