deploy
Deploy application to staging or production environments. Specify the target environment and a deployment reason to trigger security policy checks and approval gates for controlled releases.
Instructions
Deploy the application to production
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| environment | Yes | Target environment | |
| reason | No | Deployment reason |
Implementation Reference
- src/demo-server.ts:126-128 (handler)The handler case for the 'deploy' tool inside the tools/call switch statement. It generates a demo response string using args.environment and args.reason.
case 'deploy': resultText = `[demo] Deployed to ${args.environment || 'staging'}${args.reason ? ` (reason: ${args.reason})` : ''}`; break; - src/demo-server.ts:68-77 (schema)The schema/definition of the 'deploy' tool, including its name, description, and inputSchema with properties environment (enum: staging/production) and reason.
name: 'deploy', description: 'Deploy the application to production', inputSchema: { type: 'object', properties: { environment: { type: 'string', description: 'Target environment', enum: ['staging', 'production'] }, reason: { type: 'string', description: 'Deployment reason' }, }, required: ['environment'], }, - src/demo-server.ts:67-78 (registration)The 'deploy' tool is registered in the TOOLS array (line 27-79), which is returned by the tools/list handler.
{ name: 'deploy', description: 'Deploy the application to production', inputSchema: { type: 'object', properties: { environment: { type: 'string', description: 'Target environment', enum: ['staging', 'production'] }, reason: { type: 'string', description: 'Deployment reason' }, }, required: ['environment'], }, },