Skip to content

chore: list the hosted HyperFrames MCP in the official MCP registry #6408

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ukimsanov merged 1 commit into from
Oct 26, 2026
Merged

chore: list the hosted HyperFrames MCP in the official MCP registry #6408

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions server.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
{
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"name": "io.github.heygen-com/hyperframes",

@jrusso1020 jrusso1020 Oct 26, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The namespace is appropriate, but the PR body overstates who can publish and how. Current official registry authentication docs require a GitHub organization Owner, not ordinary membership. They also say plain interactive mcp-publisher login github currently cannot grant organization namespaces, even to Owners. Correct the manual plan to use an eligible Owner with appropriately scoped PAT authentication, or an authorized GitHub Actions OIDC path. After James's explicit go, a qualified org Owner should run the manual publisher from the repository root. Merging this file alone does not publish the entry.

@ukimsanov ukimsanov Oct 26, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, thanks. Checked against the auth docs and #1468: the description now says merging doesn't publish, publishing waits for James's go, and a heygen-com org Owner runs mcp-publisher login github --token <PAT> (read:org, or fine-grained Members read-only) then mcp-publisher publish, or we add the OIDC workflow later. The ordinary-member claim is gone.

"title": "HyperFrames",
"description": "Compose, edit and render HyperFrames videos (HTML to MP4) in your HeyGen account from chat clients.",
"repository": {
"url": "https://github.com/heygen-com/hyperframes",
"source": "github"
},
"websiteUrl": "https://hyperframes.heygen.com/guides/mcp",
"version": "1.0.0",
"remotes": [
{
"type": "streamable-http",
"url": "https://mcp.heygen.com/mcp/hyperframes/"
}
]
}
Loading