Agent Update

Connect

Replit Agent → Agent Update

The agent built into Replit's browser IDE. It scaffolds, edits and deploys a whole app from one prompt.

Replit Agent 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: UI: add-server dialog → Name, URL, Advanced settings → custom headers → Test & save

Setup

Add-server dialog
URL:    https://api.tryagentupdate.com/v1/mcp
Header: Authorization = Bearer au_live_...
One-click install payload — base64 it and append to https://replit.com/integrations?mcp=
{
  "displayName": "Agent Update",
  "baseUrl": "https://api.tryagentupdate.com/v1/mcp",
  "headers": [{ "key": "Authorization", "value": "Bearer au_live_..." }]
}

Before you file a bug

headers is an array of {key,value} objects here, not an object map, and the value must include the Bearer prefix. An install link embeds a live credential in a URL, so generate it client-side per user and never publish one. Replit's docs never name the transport, so verify Streamable HTTP on a real account before promising it 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.