Connect your project’s evidence.
Updated Read as Markdown ↗
MCP helps an agent reach tools and context. Factory decides how product evidence, work and verification fit together.
What Factory connects to
Each project has a project pack: its configuration and commands for reading evidence and controlling work. The pack defines how to inspect the repository, current runtime state, feedback, metrics and release status.
Factory consumes structured outputs from those commands. It is not a universal database connector. Credentials and access stay with the project or the configured tool host.
Where MCP fits
If your coding host uses MCP servers to access a database, issue tracker or documentation, those tools can help with investigation and implementation. Their availability depends on your host’s configuration and permissions.
The Factory contract remains explicit: the pack must define the evidence and checks it needs. Installing an MCP server alone does not produce a connected, verified Factory project.
Coming from the Orchestro MCP server?
The original Orchestro is a separate MCP-based project. Replacing this website does not replace your installed server, migrate its data or change its package.
There is no supported one-line switch from an Orchestro MCP configuration to a hosted Factory endpoint. Start with the Factory onboarding guide.
Documentation for agents
A short machine-readable overview of this website is available at /llms.txt. It identifies the current setup path and the distinction between implemented features and future work.