deploy_site
Sets up deployment workflow for GitHub Pages or Vercel, tracking preferences and notifying when switching deployment targets.
Instructions
Set up deployment workflow for GitHub Pages or Vercel with deployment tracking and preference learning. Use the 'target' parameter to choose one deployment platform per project (github-pages or vercel). If you switch targets, the tool will warn you to remove the old workflow file.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"repository": "<repository>"
},
"name": "deploy_site"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| repository | Yes | Repository path or URL | |
| ssg | No | Static site generator to use. If not provided, will be retrieved from knowledge graph using analysisId | |
| target | No | Deployment target: 'github-pages' (default) or 'vercel'. Vercel generates vercel.json and a Vercel CLI workflow. | github-pages |
| branch | No | gh-pages | |
| customDomain | No | ||
| invokeCliCommand | No | When true and target=vercel, includes the vercel deploy --prod CLI command in next steps | |
| projectPath | No | Local path to the project for tracking | |
| projectName | No | Project name for tracking | |
| analysisId | No | ID from repository analysis for linking | |
| userId | No | User ID for preference tracking | default |