Agent Update

Connect

Amp → Agent Update

Sourcegraph's coding agent. It runs as a terminal CLI or inside VS Code.

Amp 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: ~/.config/amp/settings.json (user) or .amp/settings.json (workspace)

Setup

~/.config/amp/settings.json
{
  "amp.mcpServers": {
    "agent-update": {
      "url": "https://api.tryagentupdate.com/v1/mcp",
      "headers": { "Authorization": "Bearer ${AGENT_UPDATE_TOKEN}" }
    }
  }
}
Or from the CLI
amp mcp add agent-update --header "Authorization=Bearer au_live_..." \
  https://api.tryagentupdate.com/v1/mcp
amp mcp doctor

Before you file a bug

The CLI --header takes Key=Value with an equals sign, not a colon. The URL is a positional argument and comes after the flags. Inside VS Code the same amp.mcpServers key goes in your normal settings.json. Workspace servers in .amp/settings.json need amp mcp approve agent-update before they load; user-scope servers don't. Precedence runs --mcp-config > .amp/settings.json > ~/.config/amp/settings.json > skills. Run amp mcp add --help once before you publish the flag form.

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