PixVerse MCP

Created By
PixVerseAIa year ago
Official PixVerse Model Context Protocol (MCP) server that enables interaction with powerful AI video generation APIs.
Overview

What is PixVerse MCP?

PixVerse MCP is the official Model Context Protocol server that enables interaction with powerful AI video generation APIs, allowing users to create high-quality videos from text or images.

How to use PixVerse MCP?

To use PixVerse MCP, obtain a PixVerse API key, install the required dependencies (Python and UV/UVX), and configure your MCP client (like Claude or Cursor) to connect to the PixVerse server.

Key features of PixVerse MCP?

  • Text-to-Video Generation: Create videos using natural language prompts.
  • Flexible Parameter Control: Customize video quality, length, and aspect ratio.
  • Co-Creation with AI Assistants: Collaborate with AI models to enhance video creation.

Use cases of PixVerse MCP?

  1. Generating creative videos from text descriptions.
  2. Creating structured videos using detailed scene descriptions.
  3. Quickly producing themed videos without extensive prompts.

FAQ from PixVerse MCP?

  • How do I get a PixVerse API key?

Register at the PixVerse Platform and generate it under "API-KEY" in your account.

  • What should I do if the server doesn't respond?

Check your API key validity and configuration file path.

  • Does MCP support image-to-video features?

Not yet; these features are available only via the PixVerse API.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
PixVerseAI
Star
-
Language
-
License
-
Category

Recommend Servers

View All
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)

a day ago