Netlify Site Config (BYOK) — connector documentation
- MCP endpoint:
https://byok-netlify-site-config.connectorbay.com/mcp - REST API:
POST https://byok-netlify-site-config.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-netlify-site-config.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Netlify Site Config personal access token, sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-netlify-site-config.connectorbay.com/health· Tool schemas:https://byok-netlify-site-config.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-netlify-site-config · agent@connectorbay.com
What Netlify Site Config (BYOK) is for
Netlify Site Config (BYOK) lets an AI assistant read your own Netlify Site Config data through the Netlify Site Config API with a key you supply (personal access token). Read-only: 7 tools (list_site_functions, list_deployed_branches, list_split_tests, get_split_test, list_snippets, list_account_env_keys, get_account_build_status). 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 Site Config. Netlify Site Config 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:
- "Which Netlify functions does my site have?"
- "Which branches of my Netlify site are deployed?"
- "Is a traffic split running on my Netlify site?"
- "How is traffic split in test 5f2a1b3c?"
- "Which snippets are injected into my Netlify site?"
- "Which environment variables are defined for my Netlify team?"
What it does
list_site_functions: List the functions deployed on a Netlify site, per deploy: branch, provider, log type, function list and creation time.list_deployed_branches: List the branches deployed for a Netlify site with branch name, slug, URL and deploy id.list_split_tests: List the branch split tests (traffic splits) of a Netlify site with path, branches, percentages and active flag.get_split_test: Get one branch split test of a Netlify site.list_snippets: List the script snippets injected on a Netlify site with id, title and positions (HTML code is not returned).list_account_env_keys: List the environment variable names of a team with scopes, secret flag, update time and who updated them. Values are never returned.get_account_build_status: Get the team's build status: active and pending builds, enqueued builds, build count and minutes used.
BYOK key
You bring your own Netlify Site Config 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
- https://open-api.netlify.com/ (the API this connector calls, with a BYOK key)
Live from the Netlify Site Config 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 Site Config. Netlify Site Config 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 Site Config account.
Built for: Worldwide. Languages: English.