Agent Update

Connect

Continue → Agent Update

An open-source AI code assistant for VS Code and JetBrains, configured entirely in YAML.

Continue 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: ~/.continue/config.yaml or .continue/mcpServers/agent-update.yaml

Setup

~/.continue/config.yaml
mcpServers:
  - name: agent-update
    type: streamable-http
    url: https://api.tryagentupdate.com/v1/mcp
    apiKey: au_live_...            # or ${{ secrets.AGENT_UPDATE_TOKEN }}

Before you file a bug

It is YAML, and mcpServers is a list. The leading dash is load-bearing. apiKey takes the raw token: Continue builds the Bearer header itself, so prefixing it yourself gives you Bearer Bearer … and a 401. Interpolation is ${{ secrets.NAME }} and resolves through Continue Hub. The requestOptions.headers escape hatch exists but has no doc or test coverage on streamable-http; its only tested example was type: sse. Treat it as a fallback, and remove apiKey if you use it. A top-level headers: key is silently ignored.

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