System Tools
5 tools for deploying your application and managing environments.
Deployment costs credits
Each deployment operation consumes credits from your balance. Make sure your code is ready before deploying.
system_DEPLOY_FRONTENDDeploy the frontend Next.js application to production. This builds and publishes your frontend.
Parameters
projectId | string | Required | The project ID |
Returns
Deployment URL and status
Example
{
"projectId": "abc123"
}
// Returns
{
"success": true,
"url": "https://myapp.appsai.com",
"deploymentId": "dep_xyz789",
"duration": "45s"
}system_DEPLOY_BACKENDDeploy the backend Parse Server to production. This publishes your cloud functions.
Parameters
projectId | string | Required | The project ID |
Returns
Deployment URL and status
Example
{
"projectId": "abc123"
}
// Returns
{
"success": true,
"url": "https://api.myapp.appsai.com",
"deploymentId": "dep_abc456",
"duration": "30s"
}system_DEPLOY_ALLDeploy both frontend and backend in a single operation. Useful for coordinated releases.
Parameters
projectId | string | Required | The project ID |
Returns
Deployment URLs and status for both
Example
{
"projectId": "abc123"
}
// Returns
{
"success": true,
"frontend": {
"url": "https://myapp.appsai.com",
"deploymentId": "dep_xyz789"
},
"backend": {
"url": "https://api.myapp.appsai.com",
"deploymentId": "dep_abc456"
}
}system_GET_ENVIRONMENT_STATUSGet the current deployment status and environment information for a project.
Parameters
projectId | string | Required | The project ID |
Returns
Environment details and deployment history
Example
{
"projectId": "abc123"
}
// Returns
{
"frontend": {
"url": "https://myapp.appsai.com",
"status": "deployed",
"lastDeployed": "2024-01-20T15:30:00Z",
"version": "v1.2.3"
},
"backend": {
"url": "https://api.myapp.appsai.com",
"status": "deployed",
"lastDeployed": "2024-01-19T10:00:00Z",
"version": "v1.1.0"
}
}system_GET_DEPLOY_ARTIFACTSGet the build artifacts and logs from recent deployments.
Parameters
projectId | string | Required | The project ID |
deploymentId | string | Optional | Specific deployment ID (default: latest) |
Returns
Build logs, artifacts, and deployment metadata
Example
{
"projectId": "abc123",
"deploymentId": "dep_xyz789"
}
// Returns
{
"deploymentId": "dep_xyz789",
"type": "frontend",
"status": "success",
"startedAt": "2024-01-20T15:25:00Z",
"completedAt": "2024-01-20T15:30:00Z",
"logs": [
"Installing dependencies...",
"Building Next.js application...",
"Optimizing images...",
"Deploying to CDN...",
"Deployment complete!"
]
}Recommended Workflow
Make and test changes
Use canvas and server tools to make your changes. Use server_RUN_BUILD to catch TypeScript errors.
Check environment status
Use system_GET_ENVIRONMENT_STATUS to see what's currently deployed.
Deploy
Use system_DEPLOY_FRONTEND, system_DEPLOY_BACKEND, or system_DEPLOY_ALL based on what changed.
Verify deployment
Check the returned URL to verify your changes are live. Use system_GET_DEPLOY_ARTIFACTS if you need to debug.