Server Name
Magic Hour
Upstream Repository or Homepage
https://github.com/magichourhq/magic-hour-mcp
What would you use it for?
Let AI clients create and edit video, image, and audio assets through Magic Hour—for example, generating a short video from a prompt, creating an image, or producing speech—without leaving the agent workflow.
Transport (if known)
http (remote URL)
Categories (pick any that fit)
Additional Context
First-party server from Magic Hour. Canonical hosted Streamable HTTP endpoint: https://mcp.magichour.ai/
Documentation: https://magichour.ai/mcp
The endpoint currently completes MCP initialize with protocol version 2025-06-18 and exposes 44 tools. Authentication is OAuth 2.1 with PKCE; the server publishes RFC 9728 protected-resource metadata and RFC 8414 authorization-server metadata. The registry definition should use the hosted HTTP endpoint directly and must not invent a local npm or stdio package.
Server Name
Magic Hour
Upstream Repository or Homepage
https://github.com/magichourhq/magic-hour-mcp
What would you use it for?
Let AI clients create and edit video, image, and audio assets through Magic Hour—for example, generating a short video from a prompt, creating an image, or producing speech—without leaving the agent workflow.
Transport (if known)
http (remote URL)
Categories (pick any that fit)
Additional Context
First-party server from Magic Hour. Canonical hosted Streamable HTTP endpoint: https://mcp.magichour.ai/
Documentation: https://magichour.ai/mcp
The endpoint currently completes MCP initialize with protocol version 2025-06-18 and exposes 44 tools. Authentication is OAuth 2.1 with PKCE; the server publishes RFC 9728 protected-resource metadata and RFC 8414 authorization-server metadata. The registry definition should use the hosted HTTP endpoint directly and must not invent a local npm or stdio package.