Vercel MCP · Vercel

{
  "name": "search_vercel_documentation",
  "description": "Search the Vercel documentation.\n  \n  Use this tool to answer any questions about Vercel’s platform, features, and best practices, including:\n  - Core Concepts: Projects, Deployments, Git Integration, Preview Deployments, Environments\n  - Frontend & Frameworks: Next.js, SvelteKit, Nuxt, Astro, Remix, frameworks configuration and optimization\n  - APIs: REST API, Vercel SDK, Build Output API\n  - Compute: Fluid Compute, Functions, Routing Middleware, Cron Jobs, OG Image Generation, Sandbox, Data Cache\n  - AI: Vercel AI SDK, AI Gateway, MCP, v0\n  - Performance & Delivery: Edge Network, Caching, CDN, Image Optimization, Headers, Redirects, Rewrites\n  - Pricing: Plans, Spend Management, Billing\n  - Security: Audit Logs, Firewall, Bot Management, BotID, OIDC, RBAC, Secure Compute, 2FA\n  - Storage: Blog, Edge Config",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "topic": {
        "type": "string",
        "description": "Topic to focus the documentation search on (e.g., 'routing', 'data-fetching')."
      },
      "tokens": {
        "default": 2500,
        "description": "Maximum number of tokens to include in the result. Default is 2500.",
        "type": "number"
      }
    },
    "required": [
      "topic"
    ]
  }
}

{
  "name": "deploy_to_vercel",
  "description": "Deploy a small, simple project from inline file contents only when the Vercel CLI is unavailable and no usable remote git repository exists, or the user explicitly requests an inline file deployment. Prefer the Vercel 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.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "target": {
        "type": "string",
        "enum": [
          "preview",
          "production"
        ],
        "description": "Required. \"preview\" for a shareable non-production URL, or \"production\" to go live."
      },
      "name": {
        "type": "string",
        "description": "Project name. Vercel creates the project if it does not already exist."
      },
      "files": {
        "minItems": 1,
        "maxItems": 300,
        "type": "array",
        "items": {
          "type": "object",
          "properties": {
            "file": {
              "type": "string",
              "description": "Root-relative POSIX path, e.g. \"app/page.tsx\"."
            },
            "data": {
              "type": "string",
              "description": "File contents: plain text, or base64 when encoding is \"base64\"."
            },
            "encoding": {
              "description": "Content encoding. Defaults to \"utf-8\"; use \"base64\" for binary files.",
              "type": "string",
              "enum": [
                "utf-8",
                "base64"
              ]
            }
          },
          "required": [
            "file",
            "data"
          ]
        },
        "description": "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. Vercel installs dependencies and builds."
      },
      "teamId": {
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool",
        "type": "string"
      },
      "projectSettings": {
        "description": "Optional build settings. Omit to let Vercel auto-detect the framework.",
        "type": "object",
        "properties": {
          "framework": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ]
          },
          "buildCommand": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ]
          },
          "installCommand": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ]
          },
          "outputDirectory": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ]
          },
          "rootDirectory": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ]
          }
        }
      }
    },
    "required": [
      "target",
      "name",
      "files"
    ]
  }
}

{
  "name": "get_git_deployment_context",
  "description": "Lists the user's Vercel teams with each team's plan, connected Cursor Origin workspaces, and linked Git projects.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {}
  }
}

{
  "name": "list_projects",
  "description": "List all Vercel projects for a user (with a max of 50). Use this to help discover the Project ID of the project that the user is working on.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      }
    },
    "required": [
      "teamId"
    ]
  }
}

{
  "name": "get_project",
  "description": "Get a specific project in Vercel",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "projectId": {
        "type": "string",
        "description": "The project ID to get the deployment events for. Alternatively the project slug can be used.\nProject IDs start with \"prj_\".\nIf you do not know the project ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the projectId\n- Use the `list_projects` tool"
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      }
    },
    "required": [
      "projectId",
      "teamId"
    ]
  }
}

{
  "name": "pause_project",
  "description": "Pause a Vercel project. Its production deployment will stop serving traffic and return 503 DEPLOYMENT_PAUSED until the project is unpaused.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "projectId": {
        "type": "string",
        "description": "The project ID to get the deployment events for. Alternatively the project slug can be used.\nProject IDs start with \"prj_\".\nIf you do not know the project ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the projectId\n- Use the `list_projects` tool"
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      }
    },
    "required": [
      "projectId",
      "teamId"
    ]
  }
}

{
  "name": "unpause_project",
  "description": "Unpause a Vercel project so its production deployment can resume serving traffic and consuming metered resources.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "projectId": {
        "type": "string",
        "description": "The project ID to get the deployment events for. Alternatively the project slug can be used.\nProject IDs start with \"prj_\".\nIf you do not know the project ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the projectId\n- Use the `list_projects` tool"
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      }
    },
    "required": [
      "projectId",
      "teamId"
    ]
  }
}

{
  "name": "get_project_deployment_protection",
  "description": "Get the effective password protection, Vercel Authentication, and Trusted IP settings for a Vercel project. Password values are never returned.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "projectId": {
        "type": "string",
        "description": "The project ID to get the deployment events for. Alternatively the project slug can be used.\nProject IDs start with \"prj_\".\nIf you do not know the project ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the projectId\n- Use the `list_projects` tool"
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      }
    },
    "required": [
      "projectId",
      "teamId"
    ]
  }
}

{
  "name": "update_project_deployment_protection",
  "description": "Partially update password protection, Vercel Authentication, and Trusted IPs for a Vercel project. Omitted settings are preserved. Availability depends on the Vercel team plan and caller permissions.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "projectId": {
        "type": "string",
        "description": "The project ID to get the deployment events for. Alternatively the project slug can be used.\nProject IDs start with \"prj_\".\nIf you do not know the project ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the projectId\n- Use the `list_projects` tool"
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      },
      "passwordProtection": {
        "description": "Enable or disable password protection. Omit to preserve the current setting.",
        "oneOf": [
          {
            "type": "object",
            "properties": {
              "enabled": {
                "type": "boolean",
                "const": true
              },
              "deploymentType": {
                "type": "string",
                "enum": [
                  "all",
                  "preview",
                  "prod_deployment_urls_and_all_previews"
                ],
                "description": "Where protection applies: all deployments, previews only, or production deployment URLs and all previews."
              },
              "password": {
                "type": "string",
                "minLength": 1,
                "description": "The new password. This value is write-only and redacted."
              }
            },
            "required": [
              "enabled",
              "deploymentType",
              "password"
            ]
          },
          {
            "type": "object",
            "properties": {
              "enabled": {
                "type": "boolean",
                "const": false
              }
            },
            "required": [
              "enabled"
            ]
          }
        ]
      },
      "ssoProtection": {
        "description": "Enable or disable Vercel Authentication. Omit to preserve the current setting.",
        "oneOf": [
          {
            "type": "object",
            "properties": {
              "enabled": {
                "type": "boolean",
                "const": true
              },
              "deploymentType": {
                "type": "string",
                "enum": [
                  "all",
                  "preview",
                  "prod_deployment_urls_and_all_previews"
                ],
                "description": "Where protection applies: all deployments, previews only, or production deployment URLs and all previews."
              }
            },
            "required": [
              "enabled",
              "deploymentType"
            ]
          },
          {
            "type": "object",
            "properties": {
              "enabled": {
                "type": "boolean",
                "const": false
              }
            },
            "required": [
              "enabled"
            ]
          }
        ]
      },
      "trustedIps": {
        "description": "Enable or disable Trusted IPs. Omit to preserve the current setting.",
        "oneOf": [
          {
            "type": "object",
            "properties": {
              "enabled": {
                "type": "boolean",
                "const": true
              },
              "deploymentType": {
                "type": "string",
                "enum": [
                  "all",
                  "preview",
                  "production",
                  "prod_deployment_urls_and_all_previews"
                ],
                "description": "Where the Trusted IP allowlist applies."
              },
              "addresses": {
                "minItems": 1,
                "type": "array",
                "items": {
                  "type": "object",
                  "properties": {
                    "value": {
                      "type": "string"
                    },
                    "note": {
                      "type": "string"
                    }
                  },
                  "required": [
                    "value"
                  ]
                }
              },
              "protectionMode": {
                "type": "string",
                "enum": [
                  "additional",
                  "exclusive"
                ],
                "description": "Whether an IP match is required in addition to other protection or can bypass it."
              }
            },
            "required": [
              "enabled",
              "deploymentType",
              "addresses",
              "protectionMode"
            ]
          },
          {
            "type": "object",
            "properties": {
              "enabled": {
                "type": "boolean",
                "const": false
              }
            },
            "required": [
              "enabled"
            ]
          }
        ]
      }
    },
    "required": [
      "projectId",
      "teamId"
    ]
  }
}

{
  "name": "list_deployments",
  "description": "List all deployments for a project",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "projectId": {
        "type": "string",
        "description": "The project ID to list deployments for."
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to list deployments for."
      },
      "since": {
        "type": "number",
        "description": "Get deployments created after this timestamp."
      },
      "until": {
        "type": "number",
        "description": "Get deployments created before this timestamp."
      }
    },
    "required": [
      "projectId",
      "teamId"
    ]
  }
}

{
  "name": "get_deployment",
  "description": "Get a specific deployment by ID or URL.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "idOrUrl": {
        "type": "string",
        "description": "The unique identifier or hostname of the deployment."
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      }
    },
    "required": [
      "idOrUrl",
      "teamId"
    ]
  }
}

{
  "name": "get_deployment_build_logs",
  "description": "Get the build logs for a deployment by ID or URL, to investigate why a build failed. Returns the most recent lines by default (where build errors appear). Use errorsOnly to see just the failing lines. Omit since and until for latest logs; use since to narrow the window and omit until when the end should be the current time.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "idOrUrl": {
        "type": "string",
        "description": "The unique identifier or hostname of the deployment."
      },
      "direction": {
        "default": "tail",
        "description": "Which end of the build log to return. \"tail\" (default) returns the most recent lines, where build errors appear. \"head\" returns the earliest lines.",
        "type": "string",
        "enum": [
          "tail",
          "head"
        ]
      },
      "errorsOnly": {
        "default": false,
        "description": "Return only error, stderr, exit, and fatal events.",
        "type": "boolean"
      },
      "limit": {
        "default": 100,
        "description": "Maximum number of log lines to return. Defaults is 100.",
        "type": "number"
      },
      "since": {
        "description": "Start of the window as an ISO date or relative lookback from now (e.g. \"1h\", \"30m\").",
        "type": "string"
      },
      "until": {
        "description": "Optional end of the window as an ISO date, relative lookback, or \"now\". Omit this when the end should be the current time.",
        "type": "string"
      },
      "buildId": {
        "description": "Filter to a specific build ID (bld_...) for multi-build deployments.",
        "type": "string"
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      }
    },
    "required": [
      "idOrUrl",
      "teamId"
    ]
  }
}

{
  "name": "get_runtime_logs",
  "description": "Get runtime logs for a project or deployment. Runtime logs show application output (console.log, errors, etc.) from serverless functions and edge functions during execution. Supports filtering by environment, log level, status code, source, time range, and full-text search. For recent windows, pass since like \"30m\" or \"24h\" and omit until; until is only needed for historical end times. For wide time ranges, scope to a deploymentId for speed, or use group_by to get counts instead of individual lines. To investigate production errors specifically, prefer get_runtime_errors.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "projectId": {
        "type": "string",
        "description": "The project ID to get runtime logs for."
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      },
      "deploymentId": {
        "description": "Filter logs to a specific deployment ID or URL.",
        "type": "string"
      },
      "environment": {
        "description": "Filter by environment: \"production\" or \"preview\".",
        "type": "string",
        "enum": [
          "production",
          "preview"
        ]
      },
      "level": {
        "description": "Filter by log level(s). Can specify multiple levels.",
        "type": "array",
        "items": {
          "type": "string",
          "enum": [
            "error",
            "warning",
            "info",
            "fatal"
          ]
        }
      },
      "statusCode": {
        "description": "Filter by HTTP status code (e.g., \"500\", \"4xx\").",
        "type": "string"
      },
      "source": {
        "description": "Filter by source type(s). Can specify multiple sources.",
        "type": "array",
        "items": {
          "type": "string",
          "enum": [
            "serverless",
            "edge-function",
            "edge-middleware",
            "static"
          ]
        }
      },
      "since": {
        "description": "Start of the window as an ISO date or relative lookback from now (e.g., \"1h\", \"30m\", \"7d\"). Defaults to 24 hours ago.",
        "type": "string"
      },
      "until": {
        "description": "Optional end of the window as an ISO date, relative lookback, or \"now\". Omit this when the end should be the current time.",
        "type": "string"
      },
      "limit": {
        "description": "Maximum number of log entries to return. Defaults to 50, max 100.",
        "type": "number"
      },
      "query": {
        "description": "Full-text search query to filter logs.",
        "type": "string"
      },
      "requestId": {
        "description": "Filter by specific request ID.",
        "type": "string"
      },
      "group_by": {
        "description": "Return counts grouped by this attribute instead of individual log lines. Use for \"how many errors\", \"status code breakdown\", \"top paths\". Fast even over wide time ranges.",
        "type": "string",
        "enum": [
          "statusCode",
          "requestPath",
          "route",
          "level",
          "source",
          "deploymentId",
          "branch"
        ]
      }
    },
    "required": [
      "projectId",
      "teamId"
    ]
  }
}

{
  "name": "get_runtime_errors",
  "description": "Get grouped runtime error clusters for a project (error name, occurrence count, affected routes, sample messages, first/last seen). Use this first to answer \"why is production erroring\" — it reads a pre-aggregated table and does not time out. For recent windows, pass since like \"24h\" or \"7d\" and omit until; until is only needed for historical end times. Max 7-day range.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "projectId": {
        "type": "string",
        "description": "The project ID to get runtime errors for."
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      },
      "since": {
        "description": "Start of the window as an ISO date or relative lookback from now (e.g. \"1h\", \"24h\", \"7d\"). Defaults to 24h ago; max lookback is 7d.",
        "type": "string"
      },
      "until": {
        "description": "Optional end of the window as an ISO date, relative lookback, or \"now\". Omit this when the end should be the current time.",
        "type": "string"
      },
      "routes": {
        "description": "Comma-separated route paths to filter by (e.g. \"/api/checkout\").",
        "type": "string"
      }
    },
    "required": [
      "projectId",
      "teamId"
    ]
  }
}

{
  "name": "list_agent_run_projects",
  "description": "List projects in a Vercel team that have Agent Runs observability data for agents built with the eve framework, with run counts and average duration rollups. Use this to discover which projects have eve agent activity before drilling into a project.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      },
      "environment": {
        "description": "Agent run environment, usually \"production\" or \"preview\". Defaults to \"production\".",
        "type": "string"
      },
      "period": {
        "description": "Preset time range. Ignored when both from and to are provided. Defaults to the dashboard endpoint default.",
        "type": "string",
        "enum": [
          "5m",
          "15m",
          "1h",
          "6h",
          "12h",
          "1d",
          "3d",
          "7d",
          "14d",
          "30d",
          "90d"
        ]
      },
      "from": {
        "description": "Start time as ISO 8601, Unix seconds, Unix milliseconds, or a relative duration like \"12h\". Must be used with to.",
        "type": "string"
      },
      "to": {
        "description": "End time as ISO 8601, Unix seconds, Unix milliseconds, a relative duration like \"1h\", or \"now\". Must be used with from.",
        "type": "string"
      }
    },
    "required": [
      "teamId"
    ]
  }
}

{
  "name": "list_agent_runs",
  "description": "List Agent Runs for a Vercel project. Agent Runs are the observability layer for agents built with the eve framework. The response includes summaries, status, model, trigger, token usage, time series, and pagination metadata. Use this to find recent or matching production eve agent runs before fetching detail or trace data.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      },
      "projectId": {
        "type": "string",
        "description": "The project ID to get the deployment events for. Alternatively the project slug can be used.\nProject IDs start with \"prj_\".\nIf you do not know the project ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the projectId\n- Use the `list_projects` tool"
      },
      "environment": {
        "description": "Agent run environment, usually \"production\" or \"preview\". Defaults to \"production\".",
        "type": "string"
      },
      "period": {
        "description": "Preset time range. Ignored when both from and to are provided. Defaults to the dashboard endpoint default.",
        "type": "string",
        "enum": [
          "5m",
          "15m",
          "1h",
          "6h",
          "12h",
          "1d",
          "3d",
          "7d",
          "14d",
          "30d",
          "90d"
        ]
      },
      "from": {
        "description": "Start time as ISO 8601, Unix seconds, Unix milliseconds, or a relative duration like \"12h\". Must be used with to.",
        "type": "string"
      },
      "to": {
        "description": "End time as ISO 8601, Unix seconds, Unix milliseconds, a relative duration like \"1h\", or \"now\". Must be used with from.",
        "type": "string"
      },
      "page": {
        "description": "1-based page number. Defaults to 1.",
        "type": "number"
      },
      "pageSize": {
        "description": "Number of runs per page. The dashboard endpoint caps this at 100.",
        "type": "number"
      },
      "search": {
        "description": "Server-side title search for Agent Runs.",
        "type": "string"
      }
    },
    "required": [
      "teamId",
      "projectId"
    ]
  }
}

{
  "name": "get_agent_run",
  "description": "Get detailed metadata for a single Agent Run from an eve agent, including events, workflow metadata, usage, and subagent breakout data. Use list_agent_runs first if you need to discover a run ID.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      },
      "projectId": {
        "type": "string",
        "description": "The project ID to get the deployment events for. Alternatively the project slug can be used.\nProject IDs start with \"prj_\".\nIf you do not know the project ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the projectId\n- Use the `list_projects` tool"
      },
      "runId": {
        "type": "string",
        "description": "The Agent Run ID to inspect."
      },
      "environment": {
        "description": "Agent run environment, usually \"production\" or \"preview\". Defaults to \"production\".",
        "type": "string"
      },
      "period": {
        "description": "Preset time range. Ignored when both from and to are provided. Defaults to the dashboard endpoint default.",
        "type": "string",
        "enum": [
          "5m",
          "15m",
          "1h",
          "6h",
          "12h",
          "1d",
          "3d",
          "7d",
          "14d",
          "30d",
          "90d"
        ]
      },
      "from": {
        "description": "Start time as ISO 8601, Unix seconds, Unix milliseconds, or a relative duration like \"12h\". Must be used with to.",
        "type": "string"
      },
      "to": {
        "description": "End time as ISO 8601, Unix seconds, Unix milliseconds, a relative duration like \"1h\", or \"now\". Must be used with from.",
        "type": "string"
      }
    },
    "required": [
      "teamId",
      "projectId",
      "runId"
    ]
  }
}

{
  "name": "get_agent_run_trace",
  "description": "Get one page of the trace for a single Agent Run from an eve agent, including turns, messages, reasoning, tool calls, token usage, and tool input/output when available. To read all available turns, follow the trace payload’s later cursor until absent; use earlier to read backwards. Pages can overlap: deduplicate turns by ID, keeping the more complete turn. Use maxFieldLength: 0 to preserve full string content.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      },
      "projectId": {
        "type": "string",
        "description": "The project ID to get the deployment events for. Alternatively the project slug can be used.\nProject IDs start with \"prj_\".\nIf you do not know the project ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the projectId\n- Use the `list_projects` tool"
      },
      "runId": {
        "type": "string",
        "description": "The Agent Run ID to inspect."
      },
      "environment": {
        "description": "Agent run environment, usually \"production\" or \"preview\". Defaults to \"production\".",
        "type": "string"
      },
      "period": {
        "description": "Preset time range. Ignored when both from and to are provided. Defaults to the dashboard endpoint default.",
        "type": "string",
        "enum": [
          "5m",
          "15m",
          "1h",
          "6h",
          "12h",
          "1d",
          "3d",
          "7d",
          "14d",
          "30d",
          "90d"
        ]
      },
      "from": {
        "description": "Start time as ISO 8601, Unix seconds, Unix milliseconds, or a relative duration like \"12h\". Must be used with to.",
        "type": "string"
      },
      "to": {
        "description": "End time as ISO 8601, Unix seconds, Unix milliseconds, a relative duration like \"1h\", or \"now\". Must be used with from.",
        "type": "string"
      },
      "maxFieldLength": {
        "description": "Maximum length for individual string fields in the returned trace. Defaults to 8000; use 0 to disable truncation.",
        "type": "number"
      },
      "traceStreamId": {
        "description": "Copy streamId from the trace payload’s later or earlier object. Requires exactly one pagination cursor.",
        "type": "string",
        "minLength": 1
      },
      "traceAfterCursor": {
        "description": "Copy cursor from later to fetch the next page, with its traceStreamId.",
        "type": "string",
        "minLength": 1
      },
      "traceBeforeChunk": {
        "description": "Copy beforeChunk from earlier to fetch the previous page, with its traceStreamId.",
        "type": "integer",
        "exclusiveMinimum": 0,
        "maximum": 9007199254740991
      }
    },
    "required": [
      "teamId",
      "projectId",
      "runId"
    ]
  }
}

{
  "name": "get_web_analytics",
  "description": "Query Web Analytics for a Vercel project. Count mode returns total visitors and pageviews (or custom event count). Aggregate mode groups results over time or by dimensions such as route, requestPath, country, referrerHostname, deviceType, browserName, eventName, flags/<name>, or eventData/<property>. Web Analytics must be enabled for the project.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "teamId": {
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool",
        "type": "string"
      },
      "projectId": {
        "type": "string",
        "description": "The project ID to get the deployment events for. Alternatively the project slug can be used.\nProject IDs start with \"prj_\".\nIf you do not know the project ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the projectId\n- Use the `list_projects` tool"
      },
      "dataset": {
        "description": "Data to query: visits for automatically tracked pageviews, or events for custom events sent with track(). Defaults to visits.",
        "type": "string",
        "enum": [
          "visits",
          "events"
        ]
      },
      "mode": {
        "description": "Count returns one total. Aggregate returns rows grouped by one or two by dimensions and requires since, until, and by. Defaults to count.",
        "type": "string",
        "enum": [
          "count",
          "aggregate"
        ]
      },
      "since": {
        "description": "Start or end of the date range as a date string, ISO 8601 timestamp, or Unix timestamp in milliseconds. Since and until must be provided together.",
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "number"
          }
        ]
      },
      "until": {
        "description": "Start or end of the date range as a date string, ISO 8601 timestamp, or Unix timestamp in milliseconds. Since and until must be provided together.",
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "number"
          }
        ]
      },
      "by": {
        "description": "One or two dimensions for aggregate mode. Time dimensions: hour, day, week, month, year. Other common dimensions: country, deviceType, environment, requestPath, referrerHostname, osName, browserName, route, UTM fields, eventName, flags/<name>, and eventData/<property>.",
        "minItems": 1,
        "maxItems": 2,
        "type": "array",
        "items": {
          "type": "string"
        }
      },
      "filter": {
        "description": "OData filter expression, for example requestPath eq &#39;/pricing&#39; and country eq &#39;US&#39;, eventName eq &#39;signup&#39;, or eventData/plan eq &#39;pro&#39;.",
        "type": "string"
      },
      "limit": {
        "description": "Maximum distinct results in aggregate mode. Remaining values are grouped into Others. Defaults to 10.",
        "type": "integer",
        "minimum": 1,
        "maximum": 100
      }
    },
    "required": [
      "projectId"
    ]
  }
}

{
  "name": "get_access_to_vercel_url",
  "description": "Creates a temporary shareable link that bypasses authentication for protected Vercel deployments.\n\n  When you encounter a Vercel deployment URL (like https://myapp-abc123.vercel.app), \n  you might receive a 403 (Forbidden) error when trying to access it. \n\n  This tool generates a special URL with a '_vercel_share' parameter that allows temporary access \n  without requiring login credentials. The shareable URL will expire in 23 hours.\n  \n  When you use the returned URL, that URL will redirect and set an auth cookie.\n  If your fetch implementation does not support cookies, use the 'web_fetch_vercel_url' tool instead.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "teamId": {
        "description": "The team ID or slug that owns the deployment. Provide this for team deployments so the lookup uses the correct scope. Use list_teams if unknown.",
        "type": "string"
      },
      "url": {
        "type": "string",
        "description": "The full URL of the Vercel deployment (e.g. \"https://myapp.vercel.app\")."
      }
    },
    "required": [
      "url"
    ]
  }
}

{
  "name": "web_fetch_vercel_url",
  "description": "Fetches a Vercel deployment URL and returns the response.\n  This is useful if another web fetch tool returns 401 (Unauthorized) or 403 (Forbidden) for a Vercel URL.\n  Supports accessing deployments protected with Vercel Authentication which the user of this MCP server has access to.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "teamId": {
        "description": "The team ID or slug that owns the deployment. Provide this for team deployments so the lookup uses the correct scope. Use list_teams if unknown.",
        "type": "string"
      },
      "url": {
        "type": "string",
        "description": "The full URL of the Vercel deployment including the path (e.g. \"https://myapp.vercel.app/my-page\")."
      }
    },
    "required": [
      "url"
    ]
  }
}

{
  "name": "list_teams",
  "description": "List the user's teams. Use this to help discover the Team ID of the teams that the user is part of.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {}
  }
}

{
  "name": "import-claude-design-from-url",
  "description": "Import a design into Vercel from a publicly fetchable URL. The file is a self-contained HTML bundle with all images, fonts, and styles inlined.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "url": {
        "type": "string",
        "description": "Public HTTPS URL to the design file. Valid for ~1 hour. Fetched server-side."
      },
      "title": {
        "description": "Suggested title for the imported design.",
        "type": "string"
      },
      "claude_design_project_id": {
        "description": "Stable Claude Design project identifier. Reuse it to update the same imported Vercel project.",
        "type": "string",
        "minLength": 1
      }
    },
    "required": [
      "url"
    ]
  }
}

{
  "name": "check_domain_availability_and_price",
  "description": "Check if domain names are available for purchase and get pricing information",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "names": {
        "minItems": 1,
        "maxItems": 10,
        "type": "array",
        "items": {
          "type": "string",
          "minLength": 1
        },
        "description": "Array of domain names to check availability for (e.g., [\"example.com\", \"test.org\"])"
      }
    },
    "required": [
      "names"
    ]
  }
}

{
  "name": "get_purchase_quote",
  "description": "Read-only price quote for a Vercel purchase. NEVER charges. This is the ONLY way to obtain an idempotencyKey — the buy_* tools no longer quote and reject un-quoted calls, so this is the REQUIRED first step before any buy_* tool. It returns the cost (when Vercel exposes one) and an idempotencyKey to pass to the matching buy tool (buy_credits, buy_domain, buy_addon, buy_pro) with confirm:true within 5 minutes to execute the charge. Present the quote to the user for explicit approval (use a structured question tool such as AskUserQuestion when available) before confirming. Products with no API price (add-ons, Pro) return a priceNote and billing URL instead of a number. Every quote includes a disclosures object the assistant must relay to the user before approval: the payment method (default card on file), that taxes/fees may apply on top of the base price, the item terms, and a link to the full terms.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "product": {
        "type": "string",
        "enum": [
          "credits",
          "domain",
          "addon",
          "pro"
        ],
        "description": "Which purchase to quote."
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      },
      "creditType": {
        "description": "Required for product:credits — which credit balance to top up.",
        "type": "string",
        "enum": [
          "v0",
          "gateway",
          "agent"
        ]
      },
      "amount": {
        "description": "Required for product:credits — amount in whole US dollars (1–1000).",
        "type": "integer",
        "exclusiveMinimum": 0,
        "maximum": 1000
      },
      "domain": {
        "description": "Required for product:domain — the domain to register, e.g. \"example.com\".",
        "type": "string",
        "minLength": 1
      },
      "years": {
        "description": "For product:domain — registration term in years (defaults to the TLD minimum).",
        "type": "integer",
        "exclusiveMinimum": 0,
        "maximum": 10
      },
      "autoRenew": {
        "description": "For product:domain — whether to auto-renew at term end. Defaults to true. Cosmetic in the quote; not part of the signed idempotencyKey.",
        "type": "boolean"
      },
      "productAlias": {
        "description": "Required for product:addon — the add-on to quote. Only \"siem\" is available today.",
        "type": "string",
        "enum": [
          "siem"
        ]
      },
      "quantity": {
        "description": "Required for product:addon — number of units.",
        "type": "integer",
        "exclusiveMinimum": 0,
        "maximum": 9007199254740991
      }
    },
    "required": [
      "product",
      "teamId"
    ]
  }
}

{
  "name": "buy_pro",
  "description": "Executes a Vercel Pro upgrade previously quoted by get_purchase_quote — quoting first is REQUIRED; this tool rejects un-quoted calls. Get the quote, present it to the user for explicit approval (use a structured question tool such as AskUserQuestion when available), then call with confirm:true, the quote's idempotencyKey, and the same parameters. This starts RECURRING Pro billing immediately at the standard Pro price. The quote returns required disclosures the assistant must relay before approval: the payment method (default card on file), that taxes/fees may apply on top of the price, the subscription terms (recurring monthly charge, no trial, cancel anytime in billing settings), and a full-terms link.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      },
      "confirm": {
        "description": "Set true to execute the upgrade; requires the idempotencyKey from get_purchase_quote.",
        "type": "boolean"
      },
      "idempotencyKey": {
        "description": "The idempotencyKey returned by get_purchase_quote.",
        "type": "string"
      }
    },
    "required": [
      "teamId"
    ]
  }
}

{
  "name": "buy_credits",
  "description": "Executes a prepaid Vercel credits purchase (v0, AI Gateway, or Vercel Agent) previously quoted by get_purchase_quote — quoting first is REQUIRED; this tool rejects un-quoted calls. Get the quote, present it to the user for explicit approval (use a structured question tool such as AskUserQuestion when available), then call with confirm:true, the quote's idempotencyKey, and the same parameters. When the user has not named an amount, offer quick-picks — $10, $25, $50, or $100 — or let them enter any custom amount ($1–$1000); do not just quote the range. Some credit types require a plan: Vercel Agent credits require the team to be on Vercel Pro (use buy_pro first), and v0 credits require a paid v0 plan (set up at v0.dev); AI Gateway credits have no plan prerequisite. If the required plan is missing the purchase is rejected (nothing is charged) with guidance. The charge is immediate and non-refundable. The quote returns required disclosures the assistant must relay before approval: the payment method (default card on file), that taxes/fees may apply on top of the base price, the item terms (credits expire in one year), and a full-terms link.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "creditType": {
        "type": "string",
        "enum": [
          "v0",
          "gateway",
          "agent"
        ],
        "description": "Which credit balance to top up: v0, gateway (AI Gateway), or agent (Vercel Agent)."
      },
      "amount": {
        "type": "integer",
        "exclusiveMinimum": 0,
        "maximum": 1000,
        "description": "Amount to purchase, in whole US dollars (1–1000)."
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      },
      "confirm": {
        "description": "Set true to execute the charge; requires the idempotencyKey from get_purchase_quote.",
        "type": "boolean"
      },
      "idempotencyKey": {
        "description": "The idempotencyKey returned by get_purchase_quote.",
        "type": "string"
      }
    },
    "required": [
      "creditType",
      "amount",
      "teamId"
    ]
  }
}

{
  "name": "buy_addon",
  "description": "Executes a Vercel add-on purchase (currently only \"siem\"), by integer quantity, previously quoted by get_purchase_quote — quoting first is REQUIRED; this tool rejects un-quoted calls. Get the quote, present it to the user for explicit approval (use a structured question tool such as AskUserQuestion when available), then call with confirm:true, the quote's idempotencyKey, and the same parameters. The team must be on the Flex plan. No price quote exists for add-ons; the charge is non-refundable. The quote returns required disclosures the assistant must relay before approval: the payment method (default card on file), that taxes/fees may apply on top of the price, the item terms (Flex plan required, billed on the next invoice), and a full-terms link.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "productAlias": {
        "type": "string",
        "enum": [
          "siem"
        ],
        "description": "The add-on to purchase. Only \"siem\" is available today."
      },
      "quantity": {
        "type": "integer",
        "exclusiveMinimum": 0,
        "maximum": 9007199254740991,
        "description": "Number of units to purchase."
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      },
      "confirm": {
        "description": "Set true to execute the charge; requires the idempotencyKey from get_purchase_quote.",
        "type": "boolean"
      },
      "idempotencyKey": {
        "description": "The idempotencyKey returned by get_purchase_quote.",
        "type": "string"
      }
    },
    "required": [
      "productAlias",
      "quantity",
      "teamId"
    ]
  }
}

{
  "name": "buy_domain",
  "description": "Executes a single-domain registration previously quoted by get_purchase_quote (product:domain) — quoting first is REQUIRED; this tool rejects un-quoted calls. Get the quote, present it to the user for explicit approval (use a structured question tool such as AskUserQuestion when available), then call with confirm:true, the quote's idempotencyKey, the expectedPrice and years from the quote, and the full registrant contact to execute the non-refundable purchase. Vercel stores no reusable registrant profile, so contact details must be supplied each time. The quote returns required disclosures the assistant must relay before approval: the payment method (default card on file), that taxes/fees may apply on top of the price, the item terms (non-refundable), and, when auto-renew is on, the recurring-charge terms in disclosures.subscription (renews automatically each term at the then-current price until auto-renew is turned off), plus a full-terms link.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "domain": {
        "type": "string",
        "minLength": 1,
        "description": "The domain to register, e.g. \"example.com\"."
      },
      "years": {
        "description": "Registration term in years. Required on confirm — must match the term shown in the quote.",
        "type": "integer",
        "exclusiveMinimum": 0,
        "maximum": 10
      },
      "autoRenew": {
        "description": "Whether to auto-renew at the end of the term. Defaults to true.",
        "type": "boolean"
      },
      "expectedPrice": {
        "description": "Required on confirm: the purchasePrice (USD) from the quote. The server rejects the order if it no longer matches the live price.",
        "type": "number",
        "exclusiveMinimum": 0
      },
      "contact": {
        "description": "Registrant (WHOIS) contact. Not needed for the quote; REQUIRED on confirm. All fields must be provided.",
        "type": "object",
        "properties": {
          "firstName": {
            "type": "string",
            "minLength": 1
          },
          "lastName": {
            "type": "string",
            "minLength": 1
          },
          "email": {
            "type": "string",
            "format": "email",
            "pattern": "^(([^<>()\\[\\]\\\\.,;:\\s@\"]+(\\.[^<>()\\[\\]\\\\.,;:\\s@\"]+)*)|(\".+\"))@((\\[[0-9]{1,3}\\.[0-9]{1,3}\\.[0-9]{1,3}\\.[0-9]{1,3}])|(([a-zA-Z\\-0-9]+\\.)+[a-zA-Z]{2,}))$"
          },
          "phone": {
            "type": "string",
            "pattern": "^\\+\\d{10,15}$"
          },
          "address1": {
            "type": "string",
            "minLength": 1
          },
          "city": {
            "type": "string",
            "minLength": 1
          },
          "state": {
            "type": "string",
            "minLength": 1
          },
          "zip": {
            "type": "string",
            "minLength": 1
          },
          "country": {
            "type": "string",
            "minLength": 2,
            "maxLength": 2,
            "description": "Two-letter ISO country code, e.g. US"
          },
          "companyName": {
            "type": "string"
          }
        },
        "required": [
          "firstName",
          "lastName",
          "email",
          "phone",
          "address1",
          "city",
          "state",
          "zip",
          "country"
        ]
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      },
      "confirm": {
        "description": "Set true to execute the purchase; requires the idempotencyKey from get_purchase_quote.",
        "type": "boolean"
      },
      "idempotencyKey": {
        "description": "The idempotencyKey returned by get_purchase_quote.",
        "type": "string"
      }
    },
    "required": [
      "domain",
      "teamId"
    ]
  }
}

{
  "name": "get_domain_order",
  "description": "Get the status of a domain purchase order returned by buy_domain, to confirm whether the registration completed.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "orderId": {
        "type": "string",
        "minLength": 1,
        "description": "The orderId returned by buy_domain."
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      }
    },
    "required": [
      "orderId"
    ]
  }
}

{
  "name": "list_toolbar_threads",
  "description": "List Vercel toolbar comment threads for a team. Returns unresolved threads by default. Use this to see feedback, comments, or discussions on deployments and previews.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      },
      "projectId": {
        "description": "Filter by project ID",
        "type": "string"
      },
      "branch": {
        "description": "Filter by branch name",
        "type": "string"
      },
      "status": {
        "description": "Filter by status. Defaults to unresolved.",
        "type": "string",
        "enum": [
          "resolved",
          "unresolved"
        ]
      },
      "page": {
        "description": "Filter by page path (e.g. /docs) or glob (e.g. /docs*)",
        "type": "string"
      },
      "search": {
        "description": "Search text in comments",
        "type": "string"
      },
      "limit": {
        "description": "Maximum number of results to return. Defaults to 20.",
        "type": "number"
      },
      "offset": {
        "description": "Pagination offset",
        "type": "number"
      }
    },
    "required": [
      "teamId"
    ]
  }
}

{
  "name": "get_toolbar_thread",
  "description": "Get a specific toolbar thread by ID, including all messages and context.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "threadId": {
        "type": "string",
        "description": "The thread ID to retrieve"
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      }
    },
    "required": [
      "threadId",
      "teamId"
    ]
  }
}

{
  "name": "change_toolbar_thread_resolve_status",
  "description": "Change the resolve status of a toolbar thread. Can be used to mark a thread as resolved or unresolve a previously resolved thread.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "threadId": {
        "type": "string",
        "description": "The thread ID to update"
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      },
      "resolved": {
        "type": "boolean",
        "description": "Set to true to resolve the thread, false to unresolve it"
      }
    },
    "required": [
      "threadId",
      "teamId",
      "resolved"
    ]
  }
}

{
  "name": "reply_to_toolbar_thread",
  "description": "Add a reply message to an existing toolbar thread.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "threadId": {
        "type": "string",
        "description": "The thread ID to reply to"
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      },
      "markdown": {
        "type": "string",
        "description": "The message content in markdown format"
      }
    },
    "required": [
      "threadId",
      "teamId",
      "markdown"
    ]
  }
}

{
  "name": "edit_toolbar_message",
  "description": "Edit an existing message in a toolbar thread.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "threadId": {
        "type": "string",
        "description": "The thread ID containing the message"
      },
      "messageId": {
        "type": "string",
        "description": "The message ID to edit"
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      },
      "markdown": {
        "type": "string",
        "description": "The updated message content in markdown format"
      }
    },
    "required": [
      "threadId",
      "messageId",
      "teamId",
      "markdown"
    ]
  }
}

{
  "name": "add_toolbar_reaction",
  "description": "Add an emoji reaction to a message in a toolbar thread.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "threadId": {
        "type": "string",
        "description": "The thread ID containing the message"
      },
      "messageId": {
        "type": "string",
        "description": "The message ID to react to"
      },
      "teamId": {
        "type": "string",
        "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
      },
      "emoji": {
        "type": "string",
        "description": "The emoji to add as a reaction (e.g. 👍)"
      }
    },
    "required": [
      "threadId",
      "messageId",
      "teamId",
      "emoji"
    ]
  }
}

{
  "name": "use_vercel_cli",
  "description": "Instructs the LLM to use Vercel CLI commands with --help flag for information",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "command": {
        "description": "Specific Vercel CLI command to run.",
        "type": "string"
      },
      "action": {
        "type": "string",
        "description": "What you want to accomplish with Vercel CLI"
      }
    },
    "required": [
      "action"
    ]
  }
}

{
  "name": "list_supported_tlds",
  "description": "Get a list of TLDs supported by Vercel",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "teamId": {
        "description": "Team ID to use for this operation.",
        "type": "string",
        "example": "team_1a2b3c4d5e6f7g8h9i0j1k2l"
      }
    }
  }
}

{
  "name": "get_tld",
  "description": "Get the metadata for a specific TLD.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "tld": {
        "type": "string",
        "description": "A valid TLD name"
      },
      "teamId": {
        "description": "Team ID to use for this operation.",
        "type": "string",
        "example": "team_1a2b3c4d5e6f7g8h9i0j1k2l"
      }
    },
    "required": [
      "tld"
    ]
  }
}

{
  "name": "get_tld_price",
  "description": "Get price data for a specific TLD. This only reflects base prices for the given TLD. Premium domains may have different prices. Use the [Get price data for a domain](https://vercel.com/docs/rest-api/reference/endpoints/domains-registrar/get-price-data-for-a-domain) endpoint to get the price data for a specific domain.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "tld": {
        "type": "string",
        "description": "A valid TLD name"
      },
      "years": {
        "type": "string",
        "description": "The number of years to get the price for. If not provided, the minimum number of years for the TLD will be used."
      },
      "teamId": {
        "description": "Team ID to use for this operation.",
        "type": "string",
        "example": "team_1a2b3c4d5e6f7g8h9i0j1k2l"
      }
    },
    "required": [
      "tld"
    ]
  }
}

{
  "name": "get_contact_info_schema",
  "description": "Some TLDs require additional contact information. Use this endpoint to get the schema for the tld-specific contact information for a domain.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "domain": {
        "type": "string",
        "description": "A valid domain name"
      },
      "teamId": {
        "description": "Team ID to use for this operation.",
        "type": "string",
        "example": "team_1a2b3c4d5e6f7g8h9i0j1k2l"
      }
    },
    "required": [
      "domain"
    ]
  }
}

{
  "name": "get_domain_price",
  "description": "Get price data for a specific domain",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "domain": {
        "type": "string",
        "description": "A valid domain name"
      },
      "years": {
        "type": "string",
        "description": "The number of years to get the price for. If not provided, the minimum number of years for the TLD will be used."
      },
      "teamId": {
        "description": "Team ID to use for this operation.",
        "type": "string",
        "example": "team_1a2b3c4d5e6f7g8h9i0j1k2l"
      }
    },
    "required": [
      "domain"
    ]
  }
}

{
  "name": "get_domain_availability",
  "description": "Get availability for a specific domain. If the domain is available, it can be purchased using the [Buy a domain](https://vercel.com/docs/rest-api/reference/endpoints/domains-registrar/buy-a-domain) endpoint or the [Buy multiple domains](https://vercel.com/docs/rest-api/reference/endpoints/domains-registrar/buy-multiple-domains) endpoint.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "domain": {
        "type": "string",
        "description": "A valid domain name"
      },
      "teamId": {
        "description": "Team ID to use for this operation.",
        "type": "string",
        "example": "team_1a2b3c4d5e6f7g8h9i0j1k2l"
      }
    },
    "required": [
      "domain"
    ]
  }
}

{
  "name": "get_bulk_price",
  "description": "Get price data for multiple domains in a single request.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "teamId": {
        "description": "Team ID to use for this operation.",
        "type": "string",
        "example": "team_1a2b3c4d5e6f7g8h9i0j1k2l"
      },
      "requestBody": {
        "type": "object",
        "properties": {
          "domains": {
            "minItems": 1,
            "maxItems": 50,
            "type": "array",
            "items": {
              "type": "string",
              "description": "A valid domain name"
            },
            "title": "maxItems(50)",
            "description": "an array of at most 50 item(s)"
          },
          "years": {
            "type": "number",
            "description": "The number of years to get the price for. If not provided, the minimum number of years for the TLD will be used."
          }
        },
        "required": [
          "domains"
        ],
        "additionalProperties": false
      }
    },
    "required": [
      "requestBody"
    ]
  }
}

{
  "name": "get_bulk_availability",
  "description": "Get availability for multiple domains. If the domains are available, they can be purchased using the [Buy a domain](https://vercel.com/docs/rest-api/reference/endpoints/domains-registrar/buy-a-domain) endpoint or the [Buy multiple domains](https://vercel.com/docs/rest-api/reference/endpoints/domains-registrar/buy-multiple-domains) endpoint.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "teamId": {
        "description": "Team ID to use for this operation.",
        "type": "string",
        "example": "team_1a2b3c4d5e6f7g8h9i0j1k2l"
      },
      "requestBody": {
        "type": "object",
        "properties": {
          "domains": {
            "minItems": 1,
            "maxItems": 50,
            "type": "array",
            "items": {
              "type": "string",
              "description": "A valid domain name"
            },
            "title": "maxItems(50)",
            "description": "an array of at most 50 item(s)"
          }
        },
        "required": [
          "domains"
        ],
        "additionalProperties": false
      }
    },
    "required": [
      "requestBody"
    ]
  }
}

{
  "name": "search_domains",
  "description": "Start domain research here. Get registration availability and pricing for 1–200 exact domain names. Returns results in input order, with registration and renewal prices in USD for available domains. No authentication required.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "teamId": {
        "description": "Team ID to use for this operation.",
        "type": "string",
        "example": "team_1a2b3c4d5e6f7g8h9i0j1k2l"
      },
      "requestBody": {
        "type": "object",
        "properties": {
          "domains": {
            "minItems": 1,
            "maxItems": 200,
            "type": "array",
            "items": {
              "type": "string",
              "description": "A valid domain name"
            },
            "title": "maxItems(200)",
            "description": "an array of at most 200 item(s)"
          }
        },
        "required": [
          "domains"
        ],
        "additionalProperties": false
      }
    },
    "required": [
      "requestBody"
    ]
  }
}