Agent Update

Connect

Warp → Agent Update

A modern terminal with a built-in agent that calls MCP servers. Configured from its settings UI.

Warp 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 -> Agents -> MCP servers -> + Add

Setup

Settings UI
Settings → Agents → MCP servers → + Add → "Streamable HTTP or SSE Server (URL)" tab
Single-server tab (bare object)
{
  "agent-update": {
    "url": "https://api.tryagentupdate.com/v1/mcp",
    "headers": { "Authorization": "Bearer au_live_..." }
  }
}
Multi-server paste box and ~/.warp/.mcp.json
Wrap the same object in {"mcpServers": { … }}

Before you file a bug

Warp's property table calls url an SSE endpoint. That wording is stale: the one url field covers both, and there is no transport key. Mind the nesting. The single-server tab takes a bare {name: {...}}, while the multi-server box and ~/.warp/.mcp.json take an {"mcpServers": { … }} wrapper. Shortcut worth knowing: Warp reads ~/.claude.json and ~/.codex/config.toml directly, so anyone who already set up Claude Code or Codex can just enable "Auto-spawn servers from third-party agents". Project-scoped servers never auto-spawn and are session-scoped, so they need re-toggling after every restart. Per-server "View Logs" may contain your token.

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