MCP
Give an agent that speaks the Model Context Protocol the same conversations, as tools.
https://mcp.forge.teamClaude Code
Signs in with your Forge account the first time it connects:
claude mcp add --transport http forge https://mcp.forge.teamOr with a key:
claude mcp add --transport http forge https://mcp.forge.team \
--header "Authorization: Bearer $FORGE_API_KEY"Any other client
Add a Streamable HTTP server at the URL above. Clients that support OAuth sign in on their own; any client can send a key as a bearer header.
Tools
create_taskCreate a Forge conversation in a working folder, explicitly set the plan or execute stage, and send its kickoff message.sendSend or steer a message into an existing Forge conversation.statusRead the authored status and measured ETA interval (lowMs, remainingMs/likely, highMs, evidence confidence) plus computed scalar etaSeconds, completion state, stage, pending human gates, accepted-but-unread inputs, whether the next turn is waiting for its turn to run, and the latest assistant-text tail for one Forge conversation.listList recent active Forge conversations as concise metadata, newest first.search_conversationsSearch whole conversations across Forge, Claude, and Codex.search_messagesSearch exact messages across Forge, Claude, and Codex.read_conversationRead one Forge, Claude, or Codex conversation as paged canonical messages.scheduleArm RECURRING or LATER work in Forge, on the scheduler Forge already runs — the durable answer to "audit this every weekday at 09:00" that create_task (one-shot, fires immediately) cannot express.list_schedulesEvery schedule armed in Forge: its id, prompt, cron or one-shot time, mode and target, when it last ran and next runs, whether it is enabled, and — when it is not — WHY (a client pause, or the conversation being archived).update_scheduleEdit an armed schedule in place, or pause/resume it.cancel_scheduleDelete an armed schedule permanently.