io.clipwright/mcp

Clipwright

Is the Clipwright MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-15.

Talking-actor and faceless short videos from your AI agent, with a free quote before each render

needs auth probed 2026-11-15 · HTTP 401 · Bearer

The server needs auth, so these tool definitions were read from the publisher's open-source package npm:@clipwright/mcp-server, started in a container with placeholder values and the network off, on 2026-11-15. Tool definitions do not depend on the token, so this is what an authorized user loads, unless the server hides tools by plan or role.

Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"a Clipwright API key is required: Authorization: Bearer cw_…"}

Endpoint

https://mcp.clipwright.io/mcp (streamable-http)

Host

mcp.clipwright.io

Of a 1M window

3.4 % of a 1M context window

Getting access

OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.clipwright.io/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server mcp.clipwright.io, PKCE S256, grants authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:device_code.
Scopes mcp:read mcp:write.
Read from the server's public OAuth metadata, without a token. Method.

Repository

https://github.com/seocombat/clipwright-mcp

Website

https://clipwright.io/?ref=mcp-registry

Registry

active, updated 2026-11-12 · registry entry

Changes

2 recorded, reachable in 1 of them. A row is added when the result, the tool count or the cost changes.

Compare this server with others.