Upstash (BYOK)
Read your Upstash Redis databases, usage stats, backups, teams and audit log with BYOK
Discover
OpenAPIRead your data8 tools
Mux Video Admin (BYOK)
Read your Mux account details, delivery usage, playback restrictions, transcription vocabularies, DRM configurations and signing key IDs with your own access token
Unify Dynamics LLC
Tools8read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderMux Video Adminunofficial, not affiliated
Works withMCP · RESTany agent
Try asking
Real questions, and the tools your agent calls to answer them.
Which Mux environment and permissions does my token have?
Tools called
get_whoamiWhich Mux assets had the most delivered seconds recently?
Tools called
list_delivery_usageWhich Mux playback restrictions do I have?
Tools called
list_playback_restrictionsWhich domains may play videos under Mux playback restriction pr1?
Tools called
get_playback_restrictionWhich Mux transcription vocabularies do I have?
Tools called
list_transcription_vocabulariesWhich Mux asset does playback ID abc belong to?
Tools called
get_playback_idAbout
Mux Video Admin (BYOK) lets an AI assistant read your own Mux Video Admin data through the Mux Video Admin API with a key you supply (access token ID). Read-only: 8 tools (get_whoami, list_delivery_usage, list_playback_restrictions, get_playback_restriction, list_transcription_vocabularies, get_playback_id, list_signing_keys, list_drm_configurations). 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.mux.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Mux Video Admin. Mux Video Admin and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Mux Video Admin API (api.mux.com) with a BYOK key; documentation: https://www.mux.com/docs/api-reference/video. 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
8 tools, grouped by job. Every one is read-only or compute-only.
- Get whoamiShow which Mux organization and environment the access token belongs to, the token name and its permissions.
- List delivery usageList delivery usage per asset for the default recent window: delivered seconds, asset duration, state, quality tier and live stream.
- List playback restrictionsList playback restrictions with allowed referrer domains and user agent rules.
- Get playback restrictionGet one playback restriction by ID: allowed referrer domains and user agent rules.
- List transcription vocabulariesList transcription vocabularies (custom phrase lists for captions) with name, phrases and dates.
- Get playback idLook up a playback ID and learn whether it belongs to an asset or a live stream, its ID and its policy (public, signed or drm).
- List signing keysList the IDs and creation times of URL signing keys.
- List drm configurationsList the DRM configuration IDs of the environment.
Information
PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpoint
https://byok-mux-video-admin.connectorbay.com/mcpREST APIopenapi.json
CountryWorldwide
FunctionOther
LayerDeep connectors
Connect it to your agent
Three ways in, the same 8 tools.
MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)
https://byok-mux-video-admin.connectorbay.com/mcpREST
POST https://byok-mux-video-admin.connectorbay.com/v1/tools/<tool>OpenAI function calling
https://connectorbay.com/openai/byok-mux-video-admin.jsonOpenAI-compatible chat
https://connectorbay.com/v1/chat/completions · how it works- Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
- Key: send your access token ID in the
X-Upstream-Keyheader (get one at dashboard.mux.com). - Ask a question; the agent picks the right tool and answers from the live data.
Mux Video Admin connector: questions and answers
What is the Mux Video Admin connector?
Mux Video Admin (BYOK) lets an AI assistant read your own Mux Video Admin data through the Mux Video Admin API with a key you supply (access token… It is a hosted MCP server with 8 tools such as Get whoami, List delivery usage, List playback restrictions, Get playback restriction, List transcription vocabularies, Get playback id, published by Unify Dynamics LLC. It is independent and not affiliated with Mux Video Admin.
How do I connect Mux Video Admin to Claude, ChatGPT or Cursor?
Add the MCP endpoint https://byok-mux-video-admin.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-mux-video-admin.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-mux-video-admin.json.
Do I need a Mux Video Admin account or API key?
Yes: this is a bring-your-own-key connector. Create a access token ID at https://dashboard.mux.com/settings/access-tokens and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Is Mux Video Admin read-only?
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Is the Mux Video Admin connector free?
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
More like this
More in OtherUpstash QStash EU (BYOK)
Read your Upstash QStash queues, schedules, URL groups, delivery logs, dead letter queue and flow control on the EU Central region with your own QStash token
Upstash QStash US (BYOK)
Read your Upstash QStash queues, schedules, URL groups, delivery logs, dead letter queue and flow control on the US East region with your own QStash token
UptimeRobot (BYOK)
Read your UptimeRobot monitors, uptime and response-time statistics, incidents, maintenance windows and status pages with your own API key
UserCheck (BYOK)
Check email addresses and domains for disposable, spam, relay and role-account signals, and read your UserCheck blocklist, gates and usage with your own API key
USGS Water Data (BYOK)
Read USGS Water Data for the Nation: monitoring locations, daily and latest streamflow, gage height and field measurements with your own api.waterdata.usgs.gov key
Documentation
Back to topMux Video Admin (BYOK) — connector documentation
- MCP endpoint:
https://byok-mux-video-admin.connectorbay.com/mcp - REST API:
POST https://byok-mux-video-admin.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-mux-video-admin.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Mux Video Admin access token ID, sent in the
X-Upstream-Keyheader and the access token secret inX-Upstream-Key-2of every request (never stored, logged or cached) - Health:
https://byok-mux-video-admin.connectorbay.com/health· Tool schemas:https://byok-mux-video-admin.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-mux-video-admin · agent@connectorbay.com
What Mux Video Admin (BYOK) is for
Mux Video Admin (BYOK) lets an AI assistant read your own Mux Video Admin data through the Mux Video Admin API with a key you supply (access token ID). Read-only: 8 tools (get_whoami, list_delivery_usage, list_playback_restrictions, get_playback_restriction, list_transcription_vocabularies, get_playback_id, list_signing_keys, list_drm_configurations). 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.mux.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Mux Video Admin. Mux Video Admin 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 Mux environment and permissions does my token have?"
- "Which Mux assets had the most delivered seconds recently?"
- "Which Mux playback restrictions do I have?"
- "Which domains may play videos under Mux playback restriction pr1?"
- "Which Mux transcription vocabularies do I have?"
- "Which Mux asset does playback ID abc belong to?"
What it does
get_whoami: Show which Mux organization and environment the access token belongs to, the token name and its permissions.list_delivery_usage: List delivery usage per asset for the default recent window: delivered seconds, asset duration, state, quality tier and live stream. Used to see which videos drive delivery volume.list_playback_restrictions: List playback restrictions with allowed referrer domains and user agent rules.get_playback_restriction: Get one playback restriction by ID: allowed referrer domains and user agent rules.list_transcription_vocabularies: List transcription vocabularies (custom phrase lists for captions) with name, phrases and dates.get_playback_id: Look up a playback ID and learn whether it belongs to an asset or a live stream, its ID and its policy (public, signed or drm).list_signing_keys: List the IDs and creation times of URL signing keys. Private keys are never returned by Mux after creation.list_drm_configurations: List the DRM configuration IDs of the environment.
BYOK key
You bring your own Mux Video Admin access token ID (https://dashboard.mux.com/settings/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.mux.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://www.mux.com/docs/api-reference/video (the API this connector calls, with a BYOK key)
Live from the Mux Video Admin API (api.mux.com) with a BYOK key; documentation: https://www.mux.com/docs/api-reference/video. 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 Mux Video Admin. Mux Video Admin 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 Mux Video Admin account.
Built for: Worldwide. Languages: English.
Privacy policy
Back to topMux Video Admin (BYOK) — Privacy Policy
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Mux Video Admin (BYOK) is. Mux Video Admin (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Mux Video Admin data: Read your Mux account details, delivery usage, playback restrictions, transcription vocabularies, DRM configurations and signing key IDs with your own access token. You bring your own Mux Video Admin access token ID; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Mux Video Admin 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.mux.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 Mux Video Admin 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 Mux Video Admin receives. The request we make on your behalf, including the key and the arguments, under Mux Video Admin's own terms and privacy policy. Mux Video Admin acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Mux Video Admin 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 Mux Video Admin 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. Mux Video Admin (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 Mux Video Admin at any time to end all access.
Children. Mux Video Admin (BYOK) is a general-audience service operated by the adult using the assistant, under Mux Video Admin's own age rules.
Changes. We will post changes here with a new effective date.
Terms of service
Back to topMux Video Admin (BYOK) — Terms of Service
Effective 24 October 2026. These terms govern use of the Mux Video Admin (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
- The Service. Mux Video Admin (BYOK) provides: Read your Mux account details, delivery usage, playback restrictions, transcription vocabularies, DRM configurations and signing key IDs with your own access token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
- Your own key, your own account. You must use your own Mux Video Admin credentials and only access data you are allowed to access. Mux Video Admin's terms apply to your use of Mux Video Admin; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
- Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Mux Video Admin. Mux Video Admin and its logos are trademarks of their owners and are used only to say which service the connector works with.
- No advice, no guarantees. Output is the data Mux Video Admin returns, lightly trimmed; it may be incomplete, delayed or changed by Mux Video Admin. Check important facts at the source.
- Read-only. The Service does not create, change, send or delete anything in your Mux Video Admin account.
- 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 Mux Video Admin's controls, or to attack any system.
- Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Mux Video Admin may change or end its API at any time.
- Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
- Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Mux Video Admin key.
- 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 Mux Video Admin takes on your account. Our total liability is limited to US $100.
- Governing law. California law; venue in San Mateo County, California.
- Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-mux-video-admin
Support
Back to topMux Video Admin (BYOK) support
Email agent@connectorbay.com. We answer within two business days.
- MCP endpoint:
https://byok-mux-video-admin.connectorbay.com/mcp - REST API:
https://byok-mux-video-admin.connectorbay.com/openapi.json - Live status: https://byok-mux-video-admin.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. Mux Video Admin (BYOK) never asks for them.