Agent Update

Connect

Cline → Agent Update

An open-source autonomous coding agent. It runs as a VS Code extension, and more recently a CLI.

Cline 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: cline_mcp_settings.json in VS Code globalStorage — macOS ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/ · Windows %APPDATA%\Code\User\globalStorage\... · Linux ~/.config/Code/User/globalStorage/... · CLI: ~/.cline/mcp.json. Prefer the panel's Configure MCP Servers button.

Setup

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

Before you file a bug

The camelCase streamableHttp is required. Omit type, or write streamable-http (that is Roo's spelling), and Cline falls back to legacy SSE. The documented symptom is HTTP 405. There is no env interpolation — cline/cline#5147 is still open — so the token sits literally in the file. autoApprove: [] prompts on every call; add ["send_message","ask_question","check_replies"] to run unattended.

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.