Request listing in GitHub MCP Registry (github.com/mcp): Talkthrough

[korovin-aa97]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Other

Body

What are you trying to do?

Have Talkthrough included in the curated GitHub MCP Registry at https://github.com/mcp.

What did you expect to happen?

Talkthrough is already published in the Official MCP Registry, so I expected either it to become discoverable in GitHub's MCP catalog or to find a documented self-service submission path.

What happened instead?

Version 0.4.1 is active/latest in the Official MCP Registry, but searching https://github.com/mcp?search=talkthrough returns no listing. I could not find a public submission form for the curated GitHub catalog.

Server details:

• Name: Talkthrough
• Official MCP name: io.github.korovin-aa97/talkthrough-mcp
• Official Registry API: https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.korovin-aa97%2Ftalkthrough-mcp
• Repository: https://github.com/korovin-aa97/talkthrough-mcp
• Release: https://github.com/korovin-aa97/talkthrough-mcp/releases/tag/v0.4.1
• PyPI: https://pypi.org/project/talkthrough-mcp/0.4.1/
• Demo: https://youtu.be/nHfGfEiVdE8

Talkthrough is a local-first MCP server that turns narrated screen recordings, audio, and public video URLs into searchable transcripts, exact frames, OCR, wall-clock evidence, and optional speaker diarization for coding agents.

Could you please include it in the GitHub MCP Registry, or point me to the current submission path?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[PrimeNewsDaily]

That sounds like a useful addition to the GitHub MCP catalog, especially since Talkthrough is already available through the official registry. Hopefully they can clarify the submission process, much like finding the right audience matters with cold email lead generation services.

[JeevaSuryaWorks]

This looks like a valid feature request. Since Talkthrough is already available in the Official MCP Registry, the GitHub MCP catalog could either:

1. Automatically synchronize entries from the Official MCP Registry, or
2. Provide a documented submission process, such as a form or pull request template.

For discoverability, it may also help to include:

• The official MCP server name and registry identifier.
• Supported transport methods.
• Installation and configuration instructions.
• Security and permission details.
• Repository, release, and package links.
• A validation status or last-synced date.

A documented review checklist would make it clearer why a server is accepted or rejected and would help maintainers submit updates consistently. It would also be useful if the catalog displayed a link to the Official MCP Registry entry when a server is not yet included in the curated catalog.

I hope this helps. If this addresses your question, please mark it as the accepted answer.