Add OpusClip remote MCP server

[yong-opus]

MCP Server Information

Server Name: opusclip
Repository URL: https://github.com/opus-pro/opusclip-mcp
Brief Description: OpusClip turns long videos into AI-curated short clips — analyze a video, preview and edit clips, reframe to vertical, caption, export, and schedule posts to connected social accounts.

This is a remote (hosted) server, so per CONTRIBUTING.md there is no Dockerfile and no image to build.

• Endpoint: https://mcp.opus.pro/mcp
• Transport: streamable-http
• Dynamic tool discovery: yes (tools.json is [], as required for remote servers)
• Docs: https://help.opus.pro/api-reference/agent-setup

Basic Requirements

• Open Source: MIT (the plugin/launcher repo opus-pro/opusclip-mcp is MIT; the hosted service is our own product)
• MCP Compliant: Implements the MCP specification over streamable-http, including RFC 9728 protected-resource metadata for authorization discovery
• Active Development: Actively maintained; also published to the official MCP registry, npm (@opusclip/mcp) and PyPI (opusclip-mcp)
• Docker Artifact: N/A — remote server, no Dockerfile required
• Documentation: https://help.opus.pro/api-reference/agent-setup
• Security Contact: security@opus.pro

Submitter Checklist

• This server meets the basic requirements listed above
• I understand this will undergo automated and manual review.
• I have tested the MCP Server using task validate -- --name opusclip
• I have built the MCP Server using task build -- --tools opusclip — N/A, remote server has no image to build
• Test credentials — see note below

Authentication

No oauth: block is declared, and that is deliberate. The server uses the standard MCP browser-based authorization flow (dynamic client registration + PKCE), so the client performs the OAuth dance and no personal access token or secret needs to be injected by Docker. This matches the existing hosted entries in the catalog that authenticate client-side.

Verified live while preparing this PR:

POST https://mcp.opus.pro/mcp   (unauthenticated)
→ HTTP 401
   www-authenticate: Bearer error="invalid_request",
     resource_metadata="https://mcp.opus.pro/mcp/.well-known/oauth-protected-resource"

GET https://mcp.opus.pro/mcp/.well-known/oauth-protected-resource
→ {"resource":"https://mcp.opus.pro/mcp",
   "authorization_servers":["https://focused-horizon-38.authkit.app"],
   "scopes_supported":["openid","profile","email","offline_access"],
   "bearer_methods_supported":["header"],
   "resource_documentation":"https://help.opus.pro/api-reference/agent-setup"}

The server refuses unauthenticated requests immediately rather than hanging. Any reviewer can connect with a free OpusClip account through the normal sign-in flow; happy to provide a dedicated test account via the credentials form if that is preferred — just say the word.

Validation

$ go run ./cmd/validate --name opusclip
✅ Name is valid
✅ Directory is valid
✅ Title is valid
✅ YAML formatting is valid
✅ Commit pin not required (non-local server)
✅ Secrets are valid
✅ Config env is valid
✅ License validation skipped (remote server)
✅ Icon is valid
✅ Dynamic tools are valid
✅ Remote is valid
✅ OAuth dynamic configuration is valid

🤖 Generated with Claude Code