| name | cloud-mcp |
| description | MCP servers for cloud infrastructure. Connect AI agents to AWS, GCP, and Azure for deployment, management, and infrastructure automation. Use when working with cloud mcp. |
| domain | integrations |
| author | oyi77 |
| license | Apache-2.0 |
| subdomain | integrations |
| tags | ["ai-agent","api","aws","azure","cloud","gcp","integrations","mcp"] |
| version | 1.0.0 |
Cloud MCP Skill
When NOT to Use
- Task is outside your authorization scope
- You need to implement controls (use implementing-* skills)
- Task is about analysis, not action (use analyzing-* skills)
- You don't have access to target systems
- Task requires compliance expertise (consult professionals)
- Task is about defense, not offense (use defensive skills)
Overview
MCP servers enabling AI agents to interact with major cloud providers (AWS, GCP, Azure) for deployment, infrastructure management, and cloud operations.
Supported Providers: AWS, Google Cloud, Microsoft Azure
Use Cases: Deployments, infrastructure management, cloud monitoring
When to Use
Trigger phrases:
AWS MCP Setup
{
"enabled": true,
"autoRun": false,
"timeout": 30000,
"retries": 3
}
Set environment variables as needed for authentication and endpoints.
Installation
{
"mcpServers": {
"aws": {
"command": "npx",
"args": ["-y", "mcp-aws"],
"env": {
"AWS_ACCESS_KEY_ID": "${AWS_ACCESS_KEY_ID}",
"AWS_SECRET_ACCESS_KEY": "${AWS_SECRET_ACCESS_KEY}",
"AWS_REGION": "us-east-1"
}
}
}
}
AWS Tools
aws.s3.listBuckets()
aws.s3.uploadFile({
bucket: "my-bucket",
key: "uploads/file.txt",
body: "file content"
})
aws.ec2.describeInstances({
Filters: [{ Name: "instance-state-name", Values: ["running"] }]
})
aws.lambda.createFunction({
FunctionName: "my-function",
Runtime: "nodejs18.x",
Handler: "index.handler",
Code: { ZipFile: buffer }
})
aws.cloudwatch.getMetricStatistics({
Namespace: "AWS/EC2",
MetricName: "CPUUtilization",
Period: 3600,
StartTime: new Date(Date.now() - 86400000),
EndTime: new Date(),
Statistics: []
})
GCP MCP Setup
{
"enabled": true,
"autoRun": false,
"timeout": 30000,
"retries": 3
}
Set environment variables as needed for authentication and endpoints.
Installation
{
"mcpServers": {
"gcp": {
"command": "npx",
"args": ["-y", "mcp-gcp"],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "/path/to/credentials.json"
}
}
}
}
GCP Tools
gcp.compute.listInstances({
project: "my-project",
zone: "us-central1-a"
})
gcp.run.deploy({
project: "my-project",
location: "us-central1",
image: "gcr.io/my-project/container:latest"
})
gcp.storage.listBuckets({
project: "my-project"
})
gcp.functions.deploy({
entryPoint: "helloHttp",
runtime: "nodejs18",
source: "."
})
Azure MCP Setup
{
"enabled": true,
"autoRun": false,
"timeout": 30000,
"retries": 3
}
Set environment variables as needed for authentication and endpoints.
Installation
{
"mcpServers": {
"azure": {
"command": "npx",
"args": ["-y", "mcp-azure"],
"env": {
"AZURE_SUBSCRIPTION_ID": "${AZURE_SUBSCRIPTION_ID}",
"AZURE_TENANT_ID": "${AZURE_TENANT_ID}",
"AZURE_CLIENT_ID": "${AZURE_CLIENT_ID}",
"AZURE_CLIENT_SECRET": "${AZURE_CLIENT_SECRET}"
}
}
}
}
Azure Tools
azure.compute.listVMs({
resourceGroup: "my-rg"
})
azure.container.create({
resourceGroup: "my-rg",
name: "my-container",
image: "nginx:latest"
})
azure.storage.listKeys({
resourceGroup: "my-rg",
accountName: "mystorage"
})
azure.web.listApps({
resourceGroup: "my-rg"
})
Use Cases
This section covers use cases for the cloud-mcp skill.
Key operations include input validation, core processing, and output verification.
Refer to the skill overview for detailed usage instructions.
1. Auto-Scaling
Trigger: High CPU
Action:
1. Check current instances
2. Scale up
3. Monitor metrics
2. Deployment Pipeline
Trigger: Git push
Action:
1. Build container
2. Push to registry
3. Deploy to cloud
4. Run health check
3. Cost Monitoring
Schedule: Daily
Action:
1. Get cost by service
2. Compare to budget
3. Alert if overspending
4. Backup Management
Schedule: Daily backup
Action:
1. Create snapshot
2. Verify backup
3. Log results
5. Incident Response
Trigger: Alert
Action:
1. Get affected resources
2. Check logs
3. Restart if needed
4. Notify team
Infrastructure as Code
This section covers infrastructure as code for the cloud-mcp skill.
Key operations include input validation, core processing, and output verification.
Refer to the skill overview for detailed usage instructions.
Generate Terraform
terraform.generate({
provider: "aws",
resources: ["ec2", "s3", "rds"]
})
Plan Changes
terraform.plan({
template: mainTf,
variables: { environment: "prod" }
})
Apply Changes
terraform.apply({
template: mainTf,
variables: { environment: "prod" },
autoApprove: false
})
Integration with 1ai-skills
- Connects with existing toolchain via standard interfaces
- Supports webhook-based event notifications
- Compatible with CI/CD pipelines for automated workflows
- Provides structured output for downstream consumption
With CI/CD
code-reviewer → cloud-mcp → deploy
↓ ↓
Review Deploy to AWS/GCP/Azure
With Monitoring
skill-performance-monitor → cloud-mcp → auto-scale
↓ ↓
Detect issue Scale resources
With Security
vulnerability-scanner → cloud-mcp → remediate
↓ ↓
Find issues Fix automatically
Best Practices
This section covers best practices for the cloud-mcp skill.
Key operations include input validation, core processing, and output verification.
Refer to the skill overview for detailed usage instructions.
Do's
✅ Use IAM roles with minimal permissions
✅ Enable logging and monitoring
✅ Use infrastructure as code
✅ Regular security audits
Don'ts
❌ Don't expose credentials
❌ Don't use root accounts
❌ Don't skip cost monitoring
Version History
- v1.0 (2026-02-27) - Initial creation
Anti-Rationalization Table
| Rationalization | Reality |
|---|
| "I will handle auth later" | Retrofitting auth is 10x harder. Build it from day one. |
| "APIs do not change" | APIs change. Version your integrations and handle deprecations. |
| "Webhooks are optional" | Without webhooks, you miss real-time events. They are essential. |
Related Skills
- automation - Workflow automation
- deployment - Deployment pipelines
- security - Cloud security
How to Use
- Invoke the skill when relevant domain keywords appear in the request
- Provide required inputs as specified in the skill definition
- Review the output for correctness before delivering to the user
- Combine with related skills for complex multi-step workflows
Verification
After completing this skill, confirm:
Process
- Analyze the task requirements
- Apply domain expertise
- Verify output quality