Optional: add Vynly as a publish destination for MiniMax image/video outputs?

Hi - author of @vynly/mcp here (https://github.com/Vovala14/vynly-mcp).

MiniMax MCP JS is one of the cleanest image+video gen MCP servers I've come across. One gap: when the agent produces a final artifact, the file just lands on disk and the user has to do something with it.

Vynly (https://vynly.co) is a social network purpose-built for AI-generated images and short video, with a public posting API + MCP server. Free demo token on first call, no signup:

curl -X POST https://vynly.co/api/agents/demo-token

Would you consider documenting @vynly/mcp in the MiniMax-MCP-JS README as an optional publish step? "Generate with MiniMax -> post to Vynly" is a natural pattern for anyone building demo workflows.

Happy to set up a featured @minimax handle on Vynly if useful for showcasing what MiniMax-driven agents actually produce. No paid sponsorship, no obligation - just an integration that should land cleanly with your audience.

Start by reading the repository README and the issue's linked Vynly MCP and public API details. Document the optional MiniMax-to-Vynly publishing workflow, with the relevant links and demo-token command; done means a reader can understand and follow the integration from the README.