MiniMax-AI / MiniMax-AI/MiniMax-MCP-JS

[Feature Request] Add 3 missing tools: image_to_image / play_video / upload_file

Open
#22 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
130
Forks
42
PR merge metrics
No merged PRs in 30d

Description

Background

The official MiniMax API already supports the following capabilities, but minimax-mcp-js v0.0.17 does not expose them as MCP tools:

  • Image-to-Image (/v1/image/editing or similar endpoint) — transform an existing image with a text prompt + reference image(s)
  • Video playback — local playback helper for downloaded .mp4 files (currently play_audio says "Does not support video")
  • File upload — local file upload helper, useful as input for voice_clone, image_to_video, etc.

Why it matters

These are listed in multiple third-party / community docs (CSDN service docs, ModelScope MCP page) as part of the official MiniMax MCP feature set, so users expect them. Without them:

  1. Users on Claude Code / Cursor / Windsurf cannot do iterative image editing (must use external tools)
  2. Users cannot preview generated videos locally — they have to switch to Finder/Quick Look after every generate_video / image_to_video call
  3. Users have to manually upload reference files to a CDN before calling image_to_video or voice_clone

Proposed tools

1. image_to_image
  • Inputs: image_1 (reference), optional image_2..5, optional subject_image_*
  • Arguments: prompt (required), aspect_ratio, imageCount
  • Maps to: MiniMax /v1/image/editing or similar
2. play_video
  • Inputs: path (local .mp4 path)
  • Uses macOS open / Linux xdg-open / Windows start to launch the system default player (same pattern as play_audio but for video)
3. upload_file
  • Inputs: path (local file path), optional purpose (string, e.g. voice_clone, image_ref)
  • Returns: hosted URL usable as input to other tools

Request

Please consider adding these three tools in the next minor release (v0.0.18+). Happy to submit a PR if maintainers agree on the API surface — just point me at the right branch / contribution guide.


Repo cross-references that mention these tools but link to the older Python MiniMax-MCP repo:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing play_audio tool and the MCP tool registration or entry points in minimax-mcp-js. Verify the MiniMax image-editing and file-upload APIs before defining their inputs and outputs, and compare the platform-specific playback approach with the existing audio helper. Done means all three tools are exposed with documented behavior and coverage for their supported inputs and platforms.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend-api-design, cli, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.