Claude Code (.mcp.json) 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: .mcp.json at the repo root — same schema as ~/.claude.json and claude mcp add-json.
Setup
{
"mcpServers": {
"agent-update": {
"type": "http",
"url": "https://api.tryagentupdate.com/v1/mcp",
"headers": { "Authorization": "Bearer ${AGENT_UPDATE_TOKEN}" }
}
}
}export AGENT_UPDATE_TOKEN=au_live_...Before you file a bug
"type": "http" is required. A url with no type is read as a stdio server and skipped, with the error MCP server "<name>" has a "url" but no "type". An unset ${VAR} with no :-default is sent literally and 401s. Project-scoped servers need interactive approval before first use; reset it with claude mcp reset-project-choices. claude -p, the Agent SDK and cloud sessions load them without prompting. If check_replies long-polls, set "timeout" above 60000. Anything at or below 60s leaves the 60s default in place.
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.