Vercel Feature Flags (BYOK)

Vercel Feature Flags (BYOK) — connector documentation

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

What Vercel Feature Flags (BYOK) is for

Vercel Feature Flags (BYOK) lets an AI assistant read your own Vercel Feature Flags data through the Vercel Feature Flags API with a key you supply (access token). Read-only: 8 tools (list_project_flags, get_flag, list_flag_versions, list_segments, get_segment, get_flag_settings, list_team_flags, get_deployment_flags). 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.vercel.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Vercel Feature Flags. Vercel Feature Flags 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 feature flags does my Vercel project have?"
• "How is flag new-checkout configured?"
• "Who changed flag new-checkout and when?"
• "Which user segments exist for my flags?"
• "Who is in segment beta-users?"
• "Are feature flags enabled for my project?"

What it does

• list_project_flags: List the feature flags of a Vercel project with slug, kind, state, tags, variants, revision and dates.
• get_flag: Get one feature flag: kind, state, variants, per-environment rules, tags, maintainers and revision.
• list_flag_versions: List the change history of a flag: revision, changed environments, message, author and time.
• list_segments: List the targeting segments of a project with label, slug, description and which flags use them.
• get_segment: Get one segment with its include, exclude and rules definition.
• get_flag_settings: Get the project's feature flag settings: whether flags are enabled, environments, entities and flag counts.
• list_team_flags: List feature flags across a team with slug, kind, state, project and dates.
• get_deployment_flags: Get the feature flag status of a deployment: flag count and response status.

BYOK key

You bring your own Vercel Feature Flags access token (https://vercel.com/account/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.vercel.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://vercel.com/docs/rest-api/reference/endpoints/feature-flags (the API this connector calls, with a BYOK key)

Live from the Vercel Feature Flags API (api.vercel.com) with a BYOK key; documentation: https://vercel.com/docs/rest-api/reference/endpoints/feature-flags. 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 Vercel Feature Flags. Vercel Feature Flags 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 Vercel Feature Flags account.

Built for: Worldwide. Languages: English.

Vercel Feature Flags (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Vercel Feature Flags (BYOK) is. Vercel Feature Flags (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Vercel Feature Flags data: Read your Vercel feature flags, flag versions, segments and flag settings by project, team or deployment with your own access token (SDK keys are never returned). You bring your own Vercel Feature Flags access token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Vercel Feature Flags call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.vercel.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Vercel Feature Flags rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Vercel Feature Flags receives. The request we make on your behalf, including the key and the arguments, under Vercel Feature Flags's own terms and privacy policy. Vercel Feature Flags acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Vercel Feature Flags gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Vercel Feature Flags data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Vercel Feature Flags (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Vercel Feature Flags at any time to end all access.

Children. Vercel Feature Flags (BYOK) is a general-audience service operated by the adult using the assistant, under Vercel Feature Flags's own age rules.

Changes. We will post changes here with a new effective date.

Vercel Feature Flags (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Vercel Feature Flags (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Vercel Feature Flags (BYOK) provides: Read your Vercel feature flags, flag versions, segments and flag settings by project, team or deployment with your own access token (SDK keys are never returned). It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Vercel Feature Flags credentials and only access data you are allowed to access. Vercel Feature Flags's terms apply to your use of Vercel Feature Flags; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Vercel Feature Flags. Vercel Feature Flags and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Vercel Feature Flags returns, lightly trimmed; it may be incomplete, delayed or changed by Vercel Feature Flags. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Vercel Feature Flags account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Vercel Feature Flags's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Vercel Feature Flags may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Vercel Feature Flags key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Vercel Feature Flags takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-vercel-feature-flags

Vercel Feature Flags (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-vercel-feature-flags.connectorbay.com/mcp
• REST API: https://byok-vercel-feature-flags.connectorbay.com/openapi.json
• Live status: https://byok-vercel-feature-flags.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Vercel Feature Flags (BYOK) never asks for them.