Agent Update

Connect

Claude Desktop (claude_desktop_config.json) → Agent Update

Claude Desktop's local config file. It launches stdio servers only, so a remote URL needs a bridge process.

Claude Desktop (claude_desktop_config.json) 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.

Where it goes: macOS ~/Library/Application Support/Claude/claude_desktop_config.json · Windows %APPDATA%\Claude\claude_desktop_config.json (Claude menu → Settings… → Developer → Edit Config)

Setup

claude_desktop_config.json (bridge; degraded path)
{
  "mcpServers": {
    "agent-update": {
      "command": "npx",
      "args": ["-y","mcp-remote","https://api.tryagentupdate.com/v1/mcp",
               "--transport","http-only","--header","Authorization:${AU_AUTH_HEADER}"],
      "env": { "AU_AUTH_HEADER": "Bearer au_live_..." }
    }
  }
}

Before you file a bug

This file is stdio-only: no url, no type, no headers. Posts claiming otherwise are confusing it with Claude Code's .mcp.json. mcp-remote is a working third-party bridge, not something Anthropic supports. Two rules from its README. No space after Authorization:, because argument escaping is broken on Cursor and on Windows Claude Desktop. And --transport http-only, so it stops probing an SSE endpoint we do not serve. Fully quit and relaunch the app after editing. Logs live at ~/Library/Logs/Claude/mcp*.log. Try the Connectors UI first.

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