From d0632a1cd1c77944e1e484e8487c2b80024fc0d5 Mon Sep 17 00:00:00 2001 From: harryalbert Date: Thu, 20 Aug 2026 09:33:55 -0400 Subject: [PATCH 1/4] Document single-prompt Factory MCP onboarding Add a copy-pasteable agent prompt that bootstraps Factory MCP installation and hands onboarding to the guidance published by the server. Update the feature summary, onboarding examples, and tool reference for factory creation. Co-Authored-By: Warp --- src/content/docs/factories/factory-mcp.mdx | 33 ++++++++++++++++++---- 1 file changed, 28 insertions(+), 5 deletions(-) diff --git a/src/content/docs/factories/factory-mcp.mdx b/src/content/docs/factories/factory-mcp.mdx index f16cc3766..9e668d7d8 100644 --- a/src/content/docs/factories/factory-mcp.mdx +++ b/src/content/docs/factories/factory-mcp.mdx @@ -1,8 +1,8 @@ --- title: Factory MCP description: >- - Connect any coding agent to your team's factories to send in work, continue - tasks locally, and hand results back. + Connect any coding agent to create and operate your team's factories, send in + work, continue tasks locally, and hand results back. sidebar: label: "Factory MCP" --- @@ -16,7 +16,7 @@ The factory keeps a single record of each task throughout. Whether a change happ * **Send work in** - Turn anything from your local session into a factory task: a bug you found, review feedback, or a half-finished change. * **Continue a task locally** - Pull a task's context into your own checkout, work with your own tools, and return the result to the same task. * **Stay in sync** - List and search tasks, read a task's conversation, and message its [foreman](/factories/factory-agents/), the agent that orchestrates each task inside the factory. -* **Create a factory** - Set up a new factory when you know the team, repositories, and source-control details. +* **Create a factory** - Let your coding agent guide you through choosing a team, code forge, repositories, factory agents, and integrations. Factory MCP is one of several ways work enters a factory, alongside Slack, GitHub, GitLab, Linear, and Jira. See [connect your factory](/factories/connect-your-factory/) for all intake paths and [how Warp Factories work](/factories/how-factories-work/) for how tasks move through a factory. @@ -26,6 +26,24 @@ Factory MCP is one of several ways work enters a factory, alongside Slack, GitHu There is nothing to configure. When your account has access, Warp connects agent sessions to Factory MCP and handles authentication for you. +### Set up with your coding agent + +Paste this prompt into a coding agent that can run commands and configure MCP servers: + +```text +Set up a Warp Factory for me. Read https://docs.warp.dev/factories/factory-mcp.md, follow the setup instructions for your coding environment to connect to and authenticate with Factory MCP, then use Factory MCP to onboard me. +``` + +Your agent will: + +1. Check whether Factory MCP is already available. +2. Add `https://app.warp.dev/api/v1/mcp/factory` using its own MCP configuration mechanism. +3. Open the browser-based Warp authorization flow. +4. Verify the Factory MCP tools are available. +5. Use the onboarding guidance published by Factory MCP to help you select a team, repositories, factory agents, and optional integrations before creating the factory. + +Some MCP clients load newly added servers only when a new session starts. If a reload is required, the agent will tell you how to resume onboarding after the server becomes available. + ### In other MCP clients Factory MCP is a streamable HTTP server at `https://app.warp.dev/api/v1/mcp/factory`. Point any MCP client that supports remote servers at that URL; on first connect, the client opens a browser so you can sign in and approve access. @@ -76,8 +94,9 @@ Factory MCP exposes a small set of tools that your agent calls on your behalf. Y * "Send this bug to the factory, including my branch." * "What's the status of the checkout-flow task?" * "Pull down ENG-123 so we can finish it here." +* "Set up a Warp Factory for me." -The rest of this page describes what happens behind those prompts. +For factory creation, the server-provided onboarding guidance walks the agent through team selection, code-forge authorization, repositories, agent roles, optional integrations, creation, and verification. The rest of this page describes what happens behind these prompts. ## Send new work to a factory @@ -110,7 +129,11 @@ Your MCP client fetches the full input schemas from the server, and tool results | Tool | What it does | | --- | --- | | `list_factories` | Lists the factories you can access. | -| `create_factory` | Creates a factory for a team, with its repositories and source-control details. | +| `list_teams` | Lists the teams that can own a new factory. | +| `list_forge_repositories` | Lists repositories available through a team's connected GitHub or GitLab account. | +| `start_connection` | Starts or checks setup for GitHub, GitLab, Slack, Linear, or Jira. | +| `get_connection_status` | Checks whether a browser authorization flow completed. | +| `create_factory` | Creates a factory with the selected repositories, integrations, and optional factory agents. | | `list_tasks` | Lists the tasks in one factory, with filters such as creator, stage, and date. | | `search_task` | Searches task titles across all factories you can access. | | `get_task` | Reads a task's status, run history, and outputs. Accepts a task ID or a reference such as a URL, issue, pull request, or branch. With `start_working=true`, also returns local setup guidance. | From 1dae3b73f1da3c7f1b55eb334490116af62e8a2d Mon Sep 17 00:00:00 2001 From: harryalbert Date: Thu, 20 Aug 2026 11:25:55 -0400 Subject: [PATCH 2/4] Document coding-agent MCP setup lifecycles Co-Authored-By: Warp --- src/content/docs/factories/factory-mcp.mdx | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/src/content/docs/factories/factory-mcp.mdx b/src/content/docs/factories/factory-mcp.mdx index 9e668d7d8..2c331c699 100644 --- a/src/content/docs/factories/factory-mcp.mdx +++ b/src/content/docs/factories/factory-mcp.mdx @@ -37,12 +37,18 @@ Set up a Warp Factory for me. Read https://docs.warp.dev/factories/factory-mcp.m Your agent will: 1. Check whether Factory MCP is already available. -2. Add `https://app.warp.dev/api/v1/mcp/factory` using its own MCP configuration mechanism. +2. If it is not available, identify the coding environment and add `https://app.warp.dev/api/v1/mcp/factory` using that client's current MCP configuration mechanism. 3. Open the browser-based Warp authorization flow. 4. Verify the Factory MCP tools are available. 5. Use the onboarding guidance published by Factory MCP to help you select a team, repositories, factory agents, and optional integrations before creating the factory. -Some MCP clients load newly added servers only when a new session starts. If a reload is required, the agent will tell you how to resume onboarding after the server becomes available. +#### Guidance for coding agents +Before configuring anything, the agent should identify its coding environment and use that client's current MCP management mechanism. If it is unsure how the client manages MCP servers, it should check the client's help or official documentation rather than guess. + +* **Warp:** Factory MCP is built in. Use the existing connection instead of adding another server. +* **Claude Code:** A server added after the session starts is not available to that running session. After adding Factory MCP, tell the user to exit and resume the same conversation from the same directory with `claude --continue`. Once resumed, complete authentication through the client's MCP controls if needed, then continue onboarding without asking the user to restate their goal. +* **Codex:** Add Factory MCP as a remote HTTP server, use Codex's built-in OAuth flow, and confirm the server is active through its MCP controls before onboarding. Only ask the user to restart or resume if the configured server is not available to the current session. +* **Other MCP clients:** Add the remote server using the client's supported configuration and authentication flow. If the client cannot load a newly added server into the current session, explain how to restart or resume while preserving the onboarding context when possible. ### In other MCP clients From 5247fd273f0d2af6a2ffd6b954374fc8de217d29 Mon Sep 17 00:00:00 2001 From: harryalbert Date: Thu, 20 Aug 2026 14:04:49 -0400 Subject: [PATCH 3/4] Make Claude MCP scope explicit Co-Authored-By: Warp --- src/content/docs/factories/factory-mcp.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/factories/factory-mcp.mdx b/src/content/docs/factories/factory-mcp.mdx index 2c331c699..7804b9490 100644 --- a/src/content/docs/factories/factory-mcp.mdx +++ b/src/content/docs/factories/factory-mcp.mdx @@ -57,7 +57,7 @@ Factory MCP is a streamable HTTP server at `https://app.warp.dev/api/v1/mcp/fact With Claude Code: ```bash -claude mcp add --transport http warp-factory https://app.warp.dev/api/v1/mcp/factory +claude mcp add --transport http --scope local warp-factory https://app.warp.dev/api/v1/mcp/factory ``` In clients that use the `mcpServers` JSON format, such as Cursor: From ad3a57a86fa35cf63b2f87ca023425d513079e77 Mon Sep 17 00:00:00 2001 From: harryalbert Date: Fri, 21 Aug 2026 10:21:54 -0400 Subject: [PATCH 4/4] Document zero-account Factory MCP onboarding Co-Authored-By: Warp --- src/content/docs/factories/factory-mcp.mdx | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/src/content/docs/factories/factory-mcp.mdx b/src/content/docs/factories/factory-mcp.mdx index 7804b9490..ad0a1c8b4 100644 --- a/src/content/docs/factories/factory-mcp.mdx +++ b/src/content/docs/factories/factory-mcp.mdx @@ -38,15 +38,15 @@ Your agent will: 1. Check whether Factory MCP is already available. 2. If it is not available, identify the coding environment and add `https://app.warp.dev/api/v1/mcp/factory` using that client's current MCP configuration mechanism. -3. Open the browser-based Warp authorization flow. +3. Open the browser-based Warp authorization flow, where you can log in or create a Warp account. 4. Verify the Factory MCP tools are available. -5. Use the onboarding guidance published by Factory MCP to help you select a team, repositories, factory agents, and optional integrations before creating the factory. +5. Use the onboarding guidance published by Factory MCP to create or join your first team conversationally, complete browser-based Stripe funding if required, and select repositories, factory agents, and optional integrations before creating the factory. #### Guidance for coding agents Before configuring anything, the agent should identify its coding environment and use that client's current MCP management mechanism. If it is unsure how the client manages MCP servers, it should check the client's help or official documentation rather than guess. * **Warp:** Factory MCP is built in. Use the existing connection instead of adding another server. -* **Claude Code:** A server added after the session starts is not available to that running session. After adding Factory MCP, tell the user to exit and resume the same conversation from the same directory with `claude --continue`. Once resumed, complete authentication through the client's MCP controls if needed, then continue onboarding without asking the user to restate their goal. +* **Claude Code:** A server added after the session starts is not available to that running session. After adding Factory MCP, tell the user to exit and resume the same conversation from the same directory with `claude --continue`. Once resumed, complete authentication through the client's MCP controls if needed; a user without a Warp account can create one in that browser flow. Then continue onboarding without asking the user to restate their goal. * **Codex:** Add Factory MCP as a remote HTTP server, use Codex's built-in OAuth flow, and confirm the server is active through its MCP controls before onboarding. Only ask the user to restart or resume if the configured server is not available to the current session. * **Other MCP clients:** Add the remote server using the client's supported configuration and authentication flow. If the client cannot load a newly added server into the current session, explain how to restart or resume while preserving the onboarding context when possible. @@ -102,7 +102,7 @@ Factory MCP exposes a small set of tools that your agent calls on your behalf. Y * "Pull down ENG-123 so we can finish it here." * "Set up a Warp Factory for me." -For factory creation, the server-provided onboarding guidance walks the agent through team selection, code-forge authorization, repositories, agent roles, optional integrations, creation, and verification. The rest of this page describes what happens behind these prompts. +For factory creation, the server-provided onboarding guidance handles a user starting without a Warp account or team: browser signup returns to MCP authorization, the agent offers discoverable teams or asks what to call a new one, and any required Stripe checkout is verified before code-forge authorization, repositories, agent roles, optional integrations, creation, and connection testing. The rest of this page describes what happens behind these prompts. ## Send new work to a factory @@ -135,7 +135,10 @@ Your MCP client fetches the full input schemas from the server, and tool results | Tool | What it does | | --- | --- | | `list_factories` | Lists the factories you can access. | -| `list_teams` | Lists the teams that can own a new factory. | +| `list_teams` | Lists current memberships and first-time joinable team choices. | +| `create_team` | Creates the authenticated user's first team with a confirmed name. | +| `join_team` | Joins a team selected from the first-time discovery choices. | +| `get_team_funding_status` | Checks first-team credit readiness and returns the browser checkout step when required. | | `list_forge_repositories` | Lists repositories available through a team's connected GitHub or GitLab account. | | `start_connection` | Starts or checks setup for GitHub, GitLab, Slack, Linear, or Jira. | | `get_connection_status` | Checks whether a browser authorization flow completed. |