Gemini로 Google Veo 및 이미지로 비디오를 생성하십시오. 패키지 이름은 남아있다 mcp-video-generation-veo2 기존 설치에 대한; 버전 2 유지, 구성 모델 및 MCP SDK 2.

설치 및 실행

Node.js 22 또는 24을 사용하십시오. 이 저장소에서:

MCP 호스트의 경우, ** 노드가 직접 ** 절대로 dist/index.js 경로. npm start]를 stdio 아이로 시작하지 마십시오 : npm의 자체 배너는 손상시킬 수 있습니다. JSON-RPC 스트림. 설치된 패키지는 또한 mcp-video-generation-veo2를 제공합니다.

API 키는 생성에만 필요합니다. 발견, 템플릿 및 저장된 매체 접근 일 없이 1. Google 모델 액세스, 청구 및 할당량은 활성화해야합니다. 세대는 MCP 요청이 취소되거나 중단될 경우도 부과될 수 있습니다. 서버는 자동 유료 제작 요청을 추적하지 않습니다.

HTTP 및 기존 SSE 클라이언트

MCP_AUTH_TOKEN]을 최소 24 자의 임의 값으로 설정한 다음 실행:

http://127.0.0.1:3000/] 을 엽니다. 자주 묻는 질문 MCP 토큰은 메모리에 보관하고 실제 MCP 요청을 사용하여 저장된 미디어를 나열합니다.

• /mcp: MCP 2026-07-28 및 무지한 유산 스트리밍 HTTP.
• /sse 플러스 `/messages?sessionId=…

Google Veo and Gemini image MCP server

Generate videos with Google Veo and images with Gemini. The package name remains mcp-video-generation-veo2 for existing installations; version 2 uses maintained, configurable models and MCP SDK 2.

Install and run

Use Node.js 22 or 24. From this repository:

npm ci
npm run build
node dist/index.js

For an MCP host, launch node directly with the absolute dist/index.js path. Do not launch npm start as the stdio child: npm’s own banners can corrupt the JSON-RPC stream. The installed package also provides mcp-video-generation-veo2.

{
  "mcpServers": {
    "veo": {
      "command": "node",
      "args": ["/absolute/path/mcp-veo2/dist/index.js"],
      "env": {
        "GOOGLE_API_KEY": "YOUR_GOOGLE_API_KEY",
        "VIDEO_MODEL": "veo-3.1-generate-preview",
        "IMAGE_MODEL": "gemini-3.1-flash-image"
      }
    }
  }
}

An API key is needed only for generation; discovery, templates, and saved-media access work without one. Google model access, billing and quota must be enabled. Generation may incur charges even if the MCP request is cancelled or times out. The server never automatically retries a paid creation request.

HTTP and existing SSE clients

Set MCP_AUTH_TOKEN to a random value of at least 24 characters, then run:

node dist/index.js http

Open http://127.0.0.1:3000/ for the included browser connection check. It asks for the MCP token, keeps it in memory, and lists saved media using real MCP requests.

• /mcp: MCP 2026-07-28 and stateless legacy Streamable HTTP.
• /sse plus /messages?sessionId=...: legacy SSE compatibility for existing clients such as LibreChat. Each connection owns its own MCP server; request bodies are parsed once. SSE sessions expire after 10 minutes without a POST.
• node dist/index.js sse remains an alias for the same HTTP listener.
• Send Authorization: Bearer on every MCP request, including the initial SSE GET. The Google API key is a separate, server-only credential.

The default bind address is loopback. To expose the service, configure HOST, ALLOWED_HOSTS and ALLOWED_ORIGINS for the proxy deployment and terminate TLS at that proxy. Only exact configured Host values and browser origins are trusted. Each deployment and storage directory belongs to one operator; do not share its bearer token/storage across untrusted tenants. This is static bearer deployment authentication, not a complete OAuth authorization server.

Issue #5’s file:// frontend and /sse/tool/listGeneratedVideos URL were never an MCP REST API. Use the included page or an MCP client. Opaque Origin: null and hostile origins are rejected; no wildcard CORS is enabled. The old public /videos directory server has been removed.

Tools and media

All seven tool names are retained:

| Tool | Inputs |