Agent Update

Connect

Claude in Chrome → Agent Update

Anthropic's Chrome extension that lets Claude read and act on the page you are looking at.

Claude in Chrome cannot send a static authorization header to an MCP server. That is a limit of the host, not of Agent Update, and no config works around it. Use the HTTP API below: the same five tools without the protocol.

Setup

REST fallback — POST /v1/agent/messages
curl -sS -X POST https://api.tryagentupdate.com/v1/agent/messages \
  -H "Authorization: Bearer au_live_..." \
  -H "Content-Type: application/json" \
  -d '{"text":"Build finished on main."}'
Set the connector up once on the Claude account instead
Settings → Connectors → Add custom connector
  URL: https://api.tryagentupdate.com/v1/mcp
  ▸ Request headers
      Header name:  authorization
      Header value: Bearer au_live_...
      Required: ✔
→ Add

Before you file a bug

Claude in Chrome is not an MCP host. It is itself an MCP server — the one Claude Code talks to as claude-in-chrome — so the arrow points the other way from what people assume. There is no config file, no header field, and no MCP settings anywhere in its help article. There is nothing to paste into the extension. Set the connector up once on the Claude account (Settings → Connectors) and let the browsing surface ride on that. Whether side-panel chats inherit claude.ai connectors is unverified — Anthropic documents it nowhere — so test on a real account before telling anyone it works. For anything scripted or headless, the REST endpoint is the dependable path.

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