deploy_to_vercel
Deploy a small, simple project from inline file contents only when the Edgenivo CLI is unavailable and no usable remote git repository exists, or the user explicitly requests an inline file deployment. Prefer the Edgenivo CLI for local projects. It reads and uploads files directly without reproducing source as model output. If the intended source is pushed to a repository's production branch, use create_git_project. Do not reconstruct medium or large projects, binary assets, or dependency trees in tool arguments. This remote tool cannot read local paths or attachments. Files with actual contents are required. Limits: 300 files, 3 MiB per file, 4 MiB total encoded contents. Creation is asynchronous. Poll get_deployment until READY, ERROR, or CANCELED before reporting the build outcome.
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
target | string | Yes | - | Required. "preview" for a shareable non-production URL, or "production" to go live. Allowed values: "preview", "production". |
name | string | Yes | - | Project name. Edgenivo creates the project if it does not already exist. |
files | Array<object> | Yes | - | Required non-empty array of source files with their actual contents. A project name or local path alone cannot deploy. Do not include node_modules, .git, .env files, or secrets. Edgenivo installs dependencies and builds. |
teamId | string | No | - | The team ID or slug. Use the team that owns the resource. |
projectSettings | object | No | - | Optional build settings. Omit to let Edgenivo auto-detect the framework. |
This workflow is available on root connections that expose deploy_to_vercel. Project-scoped connections do not register it. Use create_deployment when your scoped connection exposes that tool.
Was this helpful?