How pixverseai/pixverse-mcp works
PixVerse MCP exposes video-generation tools to MCP clients, then routes requests through server orchestration and typed request models to a PixVerse API client. The client handles HTTP transport, uploads and generation/status operations; responses return through the server to the assistant. Major capabilities include text/image generation, extensions, transitions, lip sync, sound effects, fusion, and media uploads. The repository also offers an SSE/HTTP interface. Some feature handlers are documented in README or unsampled server sections, so those capability links are documented rather than claims about individual handler internals.
Main entry points: pixverse.py PixVerse client · server.py Tool dispatch · base.py HTTP transport · sse_server.py SSE HTTP interface
Components 13
Client interfaces
- MCP server
src/server.py - SSE HTTP interface
src/sse_server.py
Tool orchestration
- Configuration
src/config.py - Tool dispatch
src/server.py - API errors
src/exceptions.py
Generation and API
- PixVerse client
src/client/pixverse.py - HTTP transport
src/client/base.py
Models and validation
- Generation requests
src/models/requests.py - Shared types
src/models/common.py - API responses
src/models/responses.py - Parameter validation
src/utils/validation.py
Other components
- MCP client
- PixVerse API
Connections 20
- MCP client → MCP server: invokes tools
README.md - MCP server → Configuration: loads settings
src/server.py - MCP server → Tool dispatch: registers handlers
src/server.py - Tool dispatch → PixVerse client: dispatches generation
src/server.py - Tool dispatch → Generation requests: uses requests
src/server.py - Tool dispatch → API responses: formats results
src/server.py - PixVerse client → HTTP transport: inherits transport
src/client/pixverse.py - PixVerse client → Generation requests: accepts requests
src/client/pixverse.py - PixVerse client → API responses: returns responses
src/client/pixverse.py - PixVerse client → HTTP transport: sends API calls
src/client/pixverse.py - HTTP transport → PixVerse API: makes HTTP requests
src/client/base.py - HTTP transport → API errors: raises API errors
src/client/base.py - PixVerse client → API errors: raises validation errors
src/client/pixverse.py - Generation requests → Shared types: uses shared types
src/models/requests.py - Parameter validation → Shared types: checks constraints
src/utils/validation.py - Parameter validation → API errors: raises validation errors
src/utils/validation.py - MCP client → SSE HTTP interface: uses HTTP endpoints
src/sse_server.py - SSE HTTP interface → MCP server: calls MCP tools
src/sse_server.py - SSE HTTP interface → PixVerse client: checks video status
src/sse_server.py - PixVerse client → PixVerse API: supports generation and uploads
README.md