MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

Mux MCP Server

Earlier Revision First-party Confidence: High (0.90)

Mux MCP Server is an MCP server published by Mux, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. It is the first-party server from Mux. Last verified 2026-08-25.

Does Mux MCP Server support the current MCP specification (2026-07-28)?

Not yet confirmed. Mux MCP Server is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-25.

Is Mux MCP Server a first-party (official) MCP server?

Yes. Mux MCP Server is the first-party MCP server published by Mux (last verified 2026-08-25).

How do I connect to Mux MCP Server?

Mux MCP Server is available via a hosted remote endpoint at https://mcp.mux.com, the package npm:@mux/mcp, the official MCP Registry under com.mux/mcp, the source repository at https://github.com/muxinc/mux-node-sdk. Authentication: none. Transports: sse-legacy, stdio.

What tools does Mux MCP Server expose?

Mux MCP Server exposes 2 tools, including execute, search_docs (last verified 2026-08-25).

Does Mux MCP Server support MCP revision 2026-07-28?

No. Mux MCP Server was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-14).

Does Mux MCP Server support MCP revision 2025-11-25?

Yes. Mux MCP Server supports MCP revision 2025-11-25 (checked 2026-08-25).

When were Mux MCP Server's facts last verified?

2026-08-25. Each fact on this page links to the sources used to verify it.

Which tools does Mux MCP Server expose?

2 tools verified.

  • execute
  • search_docs

Mux's MCP server fronts the company's video infrastructure API and is registered as official under the DNS-verified com.mux namespace, with a local stdio package (@mux/mcp) and a hosted remote at mcp.mux.com.

Spec support is grounded first-hand and is legacy. On 2026-08-14 the hosted endpoint rejected a server/discover call at 2026-07-28 with an error naming its supported versions, the newest being 2025-11-25, and then completed a legacy initialize handshake at 2025-11-25, answering as serverInfo "mux" version 14.1.0 with tools and logging capabilities. The handshake succeeded without credentials; what authentication the tool calls themselves require was not observed, so auth is recorded as unknown.

The registry record shows the now-familiar staleness pattern: it pins @mux/mcp 12.8.0 from 2025-09-18 while npm's latest is 15.0.0 from 2026-08-12, three major versions ahead, and npm's repository field has moved from mux-node-sdk to mux-ts.

Which MCP spec revisions does Mux MCP Server support?

Mux MCP Server has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.

Spec revision Status Last checked Evidence
MCP 2026-07-28 Not supported Source
MCP 2025-11-25 Supported Source

How widely adopted is Mux MCP Server?

Ranked #232 in The MCP 500 with Adoption Index 50.12 (snapshot , methodology v1).

Measurement Value Source
Official MCP Registry yes API ·
Docker MCP Catalog no API ·
npm downloads (weekly) 245 API ·
GitHub stars 181 API ·
GitHub forks 72 API ·
Last push 2026-08-27T18:40:22Z API ·
Repository archived no API ·

Repository and package signals for Mux MCP Server

Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.

Repository as of

Created
Open issues
11
Primary language
TypeScript
License (repository)
Apache-2.0
Continuous integration
Present
Tests
Present
Security policy
Present

Declared topics: mux, node, video, video-analytics, video-processing, video-streaming — author-declared on the repository, not our taxonomy.

Package (npm) as of

Latest version
15.0.0
Last published
First published
Releases
16
License (package)
Apache-2.0
Maintainers
4
Direct dependencies
22
Unpacked size
4.6 MB
Registry signature
Signed
Build provenance
Attested

How was this verified, and what are the sources?

Verified · method: endpoint-probe · confidence 0.90 (High).

  1. Official MCP Registry record com.mux/mcp v12.8.0 (published 2025-09-18) - "The official MCP Server for the Mux API", DNS-verified com.mux namespace, npm package @mux/mcp (stdio), remote streamable-http https://mcp.mux.com, repository github.com/muxinc/mux-node-sdk - accessed
  2. Endpoint probe of https://mcp.mux.com - server/discover at 2026-07-28 rejected with JSON-RPC error -32000 "Unsupported protocol version: 2026-07-28 (supported versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)"; a follow-up initialize at 2025-11-25 answered 200 over SSE framing with protocolVersion 2025-11-25, serverInfo name "mux" version 14.1.0, and tools + logging capabilities - accessed
  3. npm package @mux/mcp - latest 15.0.0 published 2026-08-12, repository field github.com/muxinc/mux-ts; the registry record trails npm by three major versions - accessed
  4. Endpoint probe of https://mcp.mux.com - declined server/discover; negotiated 2025-11-25 via the legacy initialize handshake; tools/list returned 2 tools - accessed