SavvyCal (BYOK)
Read your SavvyCal bookings, scheduling links, open time slots and workflows with your own personal access token
Read public Vimeo channels and groups and the videos inside them with your own access token
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
list_channelsget_channellist_channel_videoslist_user_channelslist_groupsget_groupVimeo Channels (BYOK) lets an AI assistant read your own Vimeo Channels data through the Vimeo Channels API with a key you supply (Vimeo access token (public scope)). Read-only: 7 tools (list_channels, get_channel, list_channel_videos, list_user_channels, list_groups, get_group, list_group_videos). 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.vimeo.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Vimeo Channels. Vimeo Channels and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Vimeo Channels API (api.vimeo.com) with a BYOK key; documentation: https://developer.vimeo.com/api/reference/channels. Endpoints checked against that documentation on 2026-10-16.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
7 tools, grouped by job. Every one is read-only or compute-only.
https://byok-vimeo-channels.connectorbay.com/mcpThree ways in, the same 7 tools.
https://byok-vimeo-channels.connectorbay.com/mcpPOST https://byok-vimeo-channels.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-vimeo-channels.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at developer.vimeo.com).Vimeo Channels (BYOK) lets an AI assistant read your own Vimeo Channels data through the Vimeo Channels API with a key you supply (Vimeo access… It is a hosted MCP server with 7 tools such as List channels, Get channel, List channel videos, List user channels, List groups, Get group, published by Unify Dynamics LLC. It is independent and not affiliated with Vimeo Channels.
Add the MCP endpoint https://byok-vimeo-channels.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-vimeo-channels.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-vimeo-channels.json.
Yes: this is a bring-your-own-key connector. Create a Vimeo access token (public scope) at https://developer.vimeo.com/api/guides/start and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read your SavvyCal bookings, scheduling links, open time slots and workflows with your own personal access token
Read your Scanova QR codes, folders, tags, forms, lead lists, custom domains, scan analytics overview and plan with your own API key
Read your Screenly digital signage screens, their online status and reports, assets, playlists and labels with your own API token
Read your Seats.io seating charts, events, seat availability reports and booking status changes with your own secret workspace key
Read your SendFox lists, campaigns, campaign statistics, tags, custom fields, forms, automations and sender domains with your own personal access token
Read your SendGrid email statistics, templates, bounce, block, spam report and unsubscribe lists with BYOK (no sending)
https://byok-vimeo-channels.connectorbay.com/mcpPOST https://byok-vimeo-channels.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-vimeo-channels.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-vimeo-channels.connectorbay.com/health · Tool schemas: https://byok-vimeo-channels.connectorbay.com/tools.jsonVimeo Channels (BYOK) lets an AI assistant read your own Vimeo Channels data through the Vimeo Channels API with a key you supply (Vimeo access token (public scope)). Read-only: 7 tools (list_channels, get_channel, list_channel_videos, list_user_channels, list_groups, get_group, list_group_videos). 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.vimeo.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Vimeo Channels. Vimeo Channels 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:
list_channels: List or search Vimeo channels with name, description, link, privacy and dates.get_channel: Get one Vimeo channel: name, description, link, privacy and dates.list_channel_videos: List the videos in a Vimeo channel with title, duration, dates, privacy and play counts. Owner profile data is not returned.list_user_channels: List the channels a Vimeo user subscribes to, with name, description, link and dates.list_groups: List or search Vimeo groups with name, description, link, privacy and dates.get_group: Get one Vimeo group: name, description, link, privacy and dates.list_group_videos: List the videos shared in a Vimeo group with title, duration, dates, privacy and play counts. Owner profile data is not returned.You bring your own Vimeo Channels Vimeo access token (public scope) (https://developer.vimeo.com/api/guides/start). 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.vimeo.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.
Live from the Vimeo Channels API (api.vimeo.com) with a BYOK key; documentation: https://developer.vimeo.com/api/reference/channels. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Vimeo Channels. Vimeo Channels 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 Vimeo Channels account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Vimeo Channels (BYOK) is. Vimeo Channels (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Vimeo Channels data: Read public Vimeo channels and groups and the videos inside them with your own access token. You bring your own Vimeo Channels Vimeo access token (public scope); the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Vimeo Channels 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.vimeo.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 Vimeo Channels 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 Vimeo Channels receives. The request we make on your behalf, including the key and the arguments, under Vimeo Channels's own terms and privacy policy. Vimeo Channels acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Vimeo Channels 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 Vimeo Channels 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. Vimeo Channels (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 Vimeo Channels at any time to end all access.
Children. Vimeo Channels (BYOK) is a general-audience service operated by the adult using the assistant, under Vimeo Channels's own age rules.
Changes. We will post changes here with a new effective date.
Effective 24 October 2026. These terms govern use of the Vimeo Channels (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-vimeo-channels.connectorbay.com/mcphttps://byok-vimeo-channels.connectorbay.com/openapi.jsonWhen 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. Vimeo Channels (BYOK) never asks for them.