# Factory MCP

> Use the Warp Factory MCP to hand work to a software factory and collaborate with it — bundle local work and send it to the cloud, find factory tasks from a Slack thread / Linear ticket / description, and pull a task down to test or iterate locally and hand it back

- Skill: `warpdotdev/factory-mcp` (Agent Skill)
- Install (CLI): `npx skillmds@latest add warpdotdev/factory-mcp`
- Raw SKILL.md: https://api.skillmd.com/api/skills/warpdotdev/factory-mcp/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: warpdotdev (https://skillmd.com/u/warpdotdev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/warpdotdev/factory-mcp

---


# Factory MCP

The canonical Factory workflow is served by the connected `warp-factory` MCP
server so its instructions stay synchronized with the live tool schemas.

Before invoking a Factory MCP tool:

1. Confirm the `warp-factory` server and its tools are available. If they are
   unavailable, stop and tell the user that Factory MCP must be connected and
   authenticated.
2. Read `skill://warp/factory-mcp/SKILL.md`, then follow the returned skill and
   its referenced resources. If the skill cannot be read, use the server
   instructions and live tool descriptions.

Treat live tool descriptions and input schemas as authoritative.