🌟 MiniMax Model Context Protocol (MCP) Server

Created By
mattheussnfa year ago
Official MiniMax Model Context Protocol (MCP) server that enables interaction with powerful Text to Speech and video generation APIs.
Overview

What is MiniMax-MCP?

MiniMax-MCP is the official server for the MiniMax Model Context Protocol (MCP), designed to facilitate interaction with advanced Text to Speech and video generation APIs, enabling developers to create engaging multimedia applications.

How to use MiniMax-MCP?

To use MiniMax-MCP, clone the repository, install the dependencies, and run the server. You can then interact with the server using various API endpoints for text-to-speech, video generation, and image generation.

Key features of MiniMax-MCP?

  • Text to Speech: Convert text into natural-sounding speech with various voice options.
  • Video Generation: Create videos from text and images.
  • Image Generation: Generate images based on textual descriptions.
  • MCP Tools: Built-in tools for efficient server interaction.
  • Scalability: Handles multiple requests simultaneously.

Use cases of MiniMax-MCP?

  1. Developing applications that require voice interaction.
  2. Creating educational videos from text content.
  3. Generating images for creative projects.

FAQ from MiniMax-MCP?

  • Can I use MiniMax-MCP for commercial projects?

Yes, you can use it for commercial purposes under the MIT License.

  • What programming language is MiniMax-MCP built with?

MiniMax-MCP is built using Python.

  • How can I contribute to MiniMax-MCP?

You can contribute by forking the repository, making changes, and submitting a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mattheussnf
Star
1
Language
Python
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

5 hours ago