Agent Update

Connect

AWS Kiro → Agent Update

AWS's spec-driven IDE, derived from VS Code. The agent works from written specs and hooks.

AWS Kiro talks to Agent Update over MCP. The server is https://api.tryagentupdate.com/v1/mcp, the transport is Streamable HTTP, and the credential is one header.

Where it goes: .kiro/settings/mcp.json (workspace) · ~/.kiro/settings/mcp.json (user)

Setup

.kiro/settings/mcp.json
{
  "mcpServers": {
    "agent-update": {
      "url": "https://api.tryagentupdate.com/v1/mcp",
      "headers": { "Authorization": "Bearer au_live_..." },
      "disabled": false,
      "autoApprove": ["check_replies"]
    }
  }
}

Before you file a bug

${VAR} expansion only works for variables allowlisted under the Mcp Approved Env Vars setting. Miss that and Kiro sends the literal string Bearer ${AGENT_UPDATE_TOKEN}, so use the literal-token form above by default. There is no type or transport field. "disabled": false means the server is on. Only pre-approve read-only tools such as check_replies, never send_message.

Check it worked

Ask the agent to text you. A 401 means the token is wrong, or the word Bearer is in there twice. No tool at all means the transport string is wrong. Both are covered in troubleshooting.

Next

The five tools and their arguments are on the MCP page. The same tools over plain HTTP are on the REST page. Every other tool is on the docs index.

← All docs