Agent Update

Connect

Claude Connectors → Agent Update

The Claude apps for desktop, web and mobile. A remote MCP server is added as a custom connector from Settings.

Claude Connectors 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: Settings -> Connectors -> Add custom connector

Setup

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

The value box takes the complete header value. Claude adds no prefix of its own. Header auth (static_headers) is Beta and rolled out selectively, so many users see no Request headers section at all. Header names come from an allowlist (authorization, x-api-key, x-auth-token), you get at most 4 headers, and values are never shown again once saved. On Team and Enterprise an Owner adds the connector under Admin settings → Connectors and members then click Connect. That means one admin enters the credential and the whole org shares it; it is not per-user. Open bug anthropics/claude-ai-mcp#644: the custom connector ignores the configured request header and falls into a broken OAuth flow. Test on a real account before telling users this works.

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