Skip to main content

Kiro Setup Guide

After setup, you can operate CloudBase services directly from Kiro’s AI chat.

Examples:

  • "Create a users collection" - AI creates database collections automatically
  • "Deploy this function" - AI uploads and configures cloud functions
  • "Deploy the frontend to CDN" - AI uploads files and configures hosting

No need to switch to the Cloud console — you can do everything in Kiro with natural language.

Prerequisites​

Before you start, make sure you have:

Node.js and a CloudBase environment ready

Node.js: Install Node.js v18.15.0 or later:

node --version

If you don’t have it installed, download it from the Node.js website.

CloudBase environment: See Create a CloudBase environment. New users can start for free.

Client

Configure your AI tool to connect with CloudBase capabilities. Supports local and hosted connection. See connection modes.

Step 1: Install / Configure CloudBase

Use project template (recommended) - Template includes MCP configuration and AI rulesView templates

Or add this configuration to .kiro/settings/mcp.json:

json
1{
2  "mcpServers": {
3    "cloudbase": {
4      "command": "npx",
5      "args": ["@cloudbase/cloudbase-mcp@latest"],
6      "env": {
7        "INTEGRATION_IDE": "Kiro"
8      }
9    }
10  }
11}
Need help?View Kiro docs

Step 2: Chat with AI

Enter the following in your AI chat in order:

prompt
Install CloudBase Skills: run npx skills add tencentcloudbase/cloudbase-skills -y
Use CloudBase Skills: 在 Android 应用中集成 CloudBase HTTP API

Configuration​

Kiro supports two configuration scopes:

  1. Workspace scope: .kiro/settings/mcp.json - only applies to the current workspace
  2. User scope: ~/.kiro/settings/mcp.json - applies to all workspaces

If both exist, workspace config takes precedence.

Steering files (development rules)​

Kiro uses Steering files to provide project knowledge. CloudBase AI development rules are downloaded into .kiro/steering/.

Steering supports:

  • AGENTS.md: placed at the project root; Kiro reads it automatically
  • Markdown files: placed under .kiro/steering/, supports conditional loading and manual referencing

See: Kiro Steering docs

FAQ​

Q: MCP connection failed?

A: Check the config format, restart Kiro, and confirm your network.

Q: Tool count shows 0?

A: See the FAQ.

Q: Steering files don’t take effect?

A: Ensure files are under .kiro/steering/ and formatted correctly. AGENTS.md is loaded automatically.

More: FAQ

相关资源