Skip to content

[ACTION] Extend Vertex AI MCP server with Veo3 support #17766

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 25, 2025

Conversation

jcortes
Copy link
Collaborator

@jcortes jcortes commented Jul 24, 2025

WHY

Resolves #17363

Summary by CodeRabbit

  • New Features

    • Introduced video generation actions using Google Vertex AI, including generating videos from text prompts and from images.
    • Added configurable options for video generation, such as model selection, prompt, aspect ratio, duration, resolution, audio, and storage location.
    • Enabled asynchronous video generation with operation status polling and support for returning videos as base64 or via Cloud Storage.
  • Chores

    • Updated version numbers for several actions and the package.
    • Upgraded platform dependency to the latest version.

@jcortes jcortes self-assigned this Jul 24, 2025
Copy link

vercel bot commented Jul 24, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments
Name Status Preview Comments Updated (UTC)
docs-v2 ⬜️ Ignored (Inspect) Jul 24, 2025 1:18am
pipedream-docs ⬜️ Ignored (Inspect) Jul 24, 2025 1:18am
pipedream-docs-redirect-do-not-edit ⬜️ Ignored (Inspect) Jul 24, 2025 1:18am

Copy link
Contributor

coderabbitai bot commented Jul 24, 2025

Walkthrough

This update introduces new actions for generating videos using Google Vertex AI's Veo models, including support for both text and image prompts. It adds a shared module for video generation logic, extends the app definition with new model options and API methods, and increments version numbers for several existing actions and the package.

Changes

File(s) Change Summary
components/google_vertex_ai/actions/analyze-image-video/analyze-image-video.mjs Version updated from 0.0.1 to 0.0.2
components/google_vertex_ai/actions/analyze-text-sentiment/analyze-text-sentiment.mjs Version updated from 0.0.1 to 0.0.2
components/google_vertex_ai/actions/classify-text/classify-text.mjs Version updated from 0.0.1 to 0.0.2
components/google_vertex_ai/package.json Package version bumped to 0.2.0; dependency @pipedream/platform updated
components/google_vertex_ai/actions/common/generate-video.mjs New shared module for video generation logic (polling, streaming, parameters)
components/google_vertex_ai/actions/generate-video-from-image/generate-video-from-image.mjs New action: generate video from image using Veo models
components/google_vertex_ai/actions/generate-video-from-text/generate-video-from-text.mjs New action: generate video from text prompt using Veo models
components/google_vertex_ai/google_vertex_ai.app.mjs Adds model prop definition; new methods for long-running video generation and operation polling

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Action (Text/Image)
    participant Common Generate Video
    participant App (google_vertex_ai)
    participant Vertex AI API

    User->>Action (Text/Image): Provide prompt (and image)
    Action (Text/Image)->>Common Generate Video: Prepare parameters
    Common Generate Video->>App (google_vertex_ai): generateVideosLongRunning()
    App (google_vertex_ai)->>Vertex AI API: POST /predict:predictLongRunning
    Vertex AI API-->>App (google_vertex_ai): Return operation name
    App (google_vertex_ai)-->>Common Generate Video: Operation started
    loop Poll until done
        Common Generate Video->>App (google_vertex_ai): fetchOperation()
        App (google_vertex_ai)->>Vertex AI API: POST /operations/predict
        Vertex AI API-->>App (google_vertex_ai): Operation status/result
        App (google_vertex_ai)-->>Common Generate Video: Operation status/result
    end
    Common Generate Video-->>Action (Text/Image): Final result
    Action (Text/Image)-->>User: Return summary and result
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~15–20 minutes

Poem

In the garden of code, a new feature grows,
Veo videos bloom where the AI wind blows.
From text or from image, the stories now play,
With polling and models, in a magical way.
Version numbers hop, dependencies, too—
A rabbit’s delight in what you now can do! 🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

components/google_vertex_ai/actions/analyze-image-video/analyze-image-video.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:202:49)

components/google_vertex_ai/actions/analyze-text-sentiment/analyze-text-sentiment.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:202:49)

components/google_vertex_ai/actions/common/generate-video.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:202:49)

  • 4 others

Note

⚡️ Unit Test Generation - Beta

CodeRabbit's unit test generation is now available in Beta! Automatically generate comprehensive unit tests for your code changes, ensuring better test coverage and catching edge cases you might miss. Our AI analyzes your code structure and creates tests that follow best practices and your project's testing patterns. Learn more here, or just try it under ✨ Finishing Touches.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch google-vertex-ai-veo3-support

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
components/google_vertex_ai/google_vertex_ai.app.mjs (1)

36-55: Consider using a stable model as the default.

The model options are well-structured, but the default is set to a preview version (veo-3.0-generate-preview). Consider using the stable version (veo-2.0-generate-001) as the default to ensure better reliability for users.

-      default: "veo-3.0-generate-preview",
+      default: "veo-2.0-generate-001",
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fe69b0d and 5f354dd.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (8)
  • components/google_vertex_ai/actions/analyze-image-video/analyze-image-video.mjs (1 hunks)
  • components/google_vertex_ai/actions/analyze-text-sentiment/analyze-text-sentiment.mjs (1 hunks)
  • components/google_vertex_ai/actions/classify-text/classify-text.mjs (1 hunks)
  • components/google_vertex_ai/actions/common/generate-video.mjs (1 hunks)
  • components/google_vertex_ai/actions/generate-video-from-image/generate-video-from-image.mjs (1 hunks)
  • components/google_vertex_ai/actions/generate-video-from-text/generate-video-from-text.mjs (1 hunks)
  • components/google_vertex_ai/google_vertex_ai.app.mjs (2 hunks)
  • components/google_vertex_ai/package.json (2 hunks)
🧰 Additional context used
🧠 Learnings (2)
components/google_vertex_ai/package.json (1)

Learnt from: jcortes
PR: #14935
File: components/sailpoint/package.json:15-18
Timestamp: 2024-12-12T19:23:09.039Z
Learning: When developing Pipedream components, do not add built-in Node.js modules like fs to package.json dependencies, as they are native modules provided by the Node.js runtime.

components/google_vertex_ai/actions/generate-video-from-image/generate-video-from-image.mjs (1)

Learnt from: js07
PR: #17375
File: components/tinypng/actions/compress-image/compress-image.mjs:18-23
Timestamp: 2025-07-01T17:01:46.327Z
Learning: In TinyPNG compress-image action (components/tinypng/actions/compress-image/compress-image.mjs), the syncDir property uses accessMode: "read" because this action only reads input files and returns API responses without writing files to /tmp, unlike other TinyPNG actions that save processed files to disk.

🧬 Code Graph Analysis (2)
components/google_vertex_ai/actions/generate-video-from-text/generate-video-from-text.mjs (1)
components/google_vertex_ai/actions/generate-video-from-image/generate-video-from-image.mjs (3)
  • operationResponse (41-67)
  • completedOperation (74-79)
  • videoCount (89-89)
components/google_vertex_ai/actions/generate-video-from-image/generate-video-from-image.mjs (1)
components/google_vertex_ai/actions/generate-video-from-text/generate-video-from-text.mjs (3)
  • operationResponse (26-48)
  • completedOperation (55-60)
  • videoCount (70-70)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
  • GitHub Check: Verify TypeScript components
  • GitHub Check: Publish TypeScript components
  • GitHub Check: pnpm publish
  • GitHub Check: Lint Code Base
🔇 Additional comments (11)
components/google_vertex_ai/package.json (1)

3-3: LGTM! Version updates are appropriate for new feature additions.

The minor version bump (0.1.0 → 0.2.0) correctly reflects the addition of new video generation capabilities, and the platform dependency update aligns with the enhanced functionality.

Also applies to: 16-16

components/google_vertex_ai/actions/classify-text/classify-text.mjs (1)

7-7: LGTM! Coordinated version update for consistency.

The patch version bump maintains consistency across the Google Vertex AI component ecosystem as part of the release that introduces video generation capabilities.

components/google_vertex_ai/actions/analyze-image-video/analyze-image-video.mjs (1)

7-7: LGTM! Consistent version management across actions.

The version update maintains consistency with other actions in the component without introducing unnecessary changes to existing functionality.

components/google_vertex_ai/actions/analyze-text-sentiment/analyze-text-sentiment.mjs (1)

7-7: LGTM! Appropriate version synchronization.

The version update aligns with the coordinated release strategy for the Google Vertex AI component enhancements.

components/google_vertex_ai/actions/generate-video-from-image/generate-video-from-image.mjs (3)

1-2: LGTM! Imports are appropriate for the functionality.

The imports correctly include the file handling utility and the shared video generation logic.


4-18: Well-structured action metadata.

The action properly extends the common module and provides clear documentation. The image property description helpfully specifies supported formats and quality recommendations.


19-95: Solid implementation following established patterns.

The run method correctly handles image file processing, converts to base64, and follows the same async operation pattern as the text-based video generation. Error handling is comprehensive and the summary message appropriately indicates the source type.

components/google_vertex_ai/actions/common/generate-video.mjs (3)

3-113: Comprehensive and well-documented props definition.

The properties are thoughtfully defined with clear descriptions, appropriate defaults, and helpful model-specific notes (Veo 2 vs Veo 3). The validation constraints and optional flags are properly set.


115-147: Robust polling implementation with appropriate timeouts.

The polling logic uses reasonable intervals (45 seconds) and timeout (6 attempts) for video generation operations. Error handling and progress logging are well-implemented.


148-159: Standard and correct stream-to-base64 implementation.

The method properly handles stream events, efficiently concatenates chunks, and converts to base64. Error handling is appropriate.

components/google_vertex_ai/actions/generate-video-from-text/generate-video-from-text.mjs (1)

1-77: Clean implementation following established patterns.

This text-based video generation action correctly implements the same async operation pattern as the image version, with appropriate simplifications (no file handling required). The error handling, polling logic, and response processing are consistent and robust.

Copy link
Collaborator

@luancazarine luancazarine left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @jcortes, LGTM! Ready for QA!

@vunguyenhung vunguyenhung merged commit 85939a1 into master Jul 25, 2025
11 checks passed
@vunguyenhung vunguyenhung deleted the google-vertex-ai-veo3-support branch July 25, 2025 06:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[ACTION] Extend Vertex AI MCP server with Veo3 support
3 participants