Інтеграція MCP
OpenFactory підтримує Model Context Protocol , щоб AI assistants могли допомагати створювати builds, inspect recipes, manage VMs, review test results.
Use MCP when you want to work with OpenFactory from Claude, Cursor, Claude Code, OpenAI Codex, or another MCP-compatible client without switching back and forth between tools.
Requirements
- MCP client that supports remote MCP servers
- For account-backed access, sign in to OpenFactory in this browser
- For guest access, use generated guest token shown below
Account API keys shown once when created and can be revoked from console. Guest tokens are browser identifiers for metered access; they are not account secrets.
Endpoints
| Transport | URL | Use |
|---|---|---|
| Streamable HTTP | https://console.openfactory.tech/mcp-stream/mcp | The OpenFactory MCP endpoint |
Streamable HTTP is only supported transport. Older HTTP+SSE endpoints (/mcp/sse, /mcp/messages) retired and now return 410 Gone; point any client still using them at Streamable HTTP URL above, with same Authorization header. Claude Code, Claude Desktop, Cursor, Codex, and OpenCode all support Streamable HTTP.
Copy-Paste Config
Restart Claude Desktop, Cursor, OpenAI Codex, or any other long-running MCP client after changing MCP settings. OpenAI Codex reads MCP servers from ~/.codex/config.toml and connects to Streamable HTTP directly: no mcp-remote bridge needed. Claude.ai custom connectors may ask for server URL and header as separate fields.
Available Capabilities
OpenFactory exposes customer-facing tools for:
| Category | Examples |
|---|---|
| Builds | List builds, create builds from recipes, check build status, retry failed builds |
| Recipes | Browse templates, validate recipes, customize templates |
| Images | Get download links for completed artifacts |
| VMs | List VMs, create test VMs, start or stop VMs, open console links |
| Tests | Run verification, list test runs, inspect test results, manage reusable test suites |
| App UI testing | Drive tester VM to test any app URL: reusable, self-hardening GUI scenarios. No deploy required |
| App deployment | Deploy Git repo to live web app with public preview URL (https://<slug>.apps.openfactory.tech) |
Tool availability can vary by plan and organization permissions.
Reusable Test Suites
Test suites can be created before variant or ISO has been built. Define one or more test cases, custom assertions, predefined tests, named ISO target slots such as primary, client, or server. When builds ready, bind each slot to completed build and run suite.
| Tool | Use |
|---|---|
create_test_suite | Create reusable suite without requiring built variant |
list_test_suites | List suites available to current MCP user |
get_test_suite | View suite definition and recent run history |
update_test_suite_targets | Bind named ISO target slots to completed builds |
run_test_suite | Run suite against bound ISO target slots |
list_test_suite_runs | List runs created from suite |
get_test_suite_status | View authoring readiness and latest run status |
App UI Testing: any URL, no deploy
Test user interface of any web app by pointing managed tester VM at URL. You don’t deploy your app with OpenFactory to test it. Tester VM opens local dev server, preview/production deployment on Vercel, AWS, Netlify, or any host, or any public URL reachable from VM. Your app stays where it already runs.
Scenarios written in plain language and self-hardening: first run learns where each UI element is, later runs replay from memory (skipping slow visual pass). Makes replays fast and resilient to small UI changes. Scenarios support environment variables (${VAR}) and 2FA (${totp:VAR}, RFC 6238) for sign-ins; secrets passed at run time and never stored.
| Tool | Use |
|---|---|
ensure_tester_vm | Get or create persistent desktop tester VM |
create_app_scenario | Save reusable GUI scenario for app URL |
run_app_scenario | Run it (pass run-time secrets here) and record screenshots + verdict |
list_app_scenarios / get_app_scenario | Browse scenarios and hardened cache |
start_app_test / record_app_test_step / finish_app_test | Drive and record ad-hoc run yourself |
annotate_screenshot | Draw labeled highlight boxes on screenshot |
See App UI Testing for full workflow, step schema, 2FA examples.
App Deployment: Git repo to a public URL
Deploy web app straight from Git repository and get public preview URL (https://<slug>.apps.openfactory.tech) that you can open, share, or point test scenario at. OpenFactory clones repo, installs dependencies, starts app, health-checks it. Nothing to wire up: no port forwarding, tunnels, DNS.
Pairs with App UI testing: deploy app, then run scenario against preview URL, or skip deploy and test app you already host (Vercel, AWS, …).
| Tool | Use |
|---|---|
create_app | Register Git repo as app (name, source, slug) |
deploy_app | Deploy app and return public preview URL |
list_apps / get_app | Browse apps, URLs, deploy history |
iterate_app | Dispatch natural-language change to app; agent applies and redeploys |
get_app_build_status | Poll app deploy status and in-flight change tickets |
See App Deployment for full workflow. To let own users speak changes to app from mic button, see Voice Iterate Widget.
Example Prompts
Show my most recent OpenFactory builds and summarize any failures.Create a Debian server image with SSH, Docker, a deploy user, and default verification tests.Validate this recipe before I start a build.Start a VM from my latest completed build and give me the console link.Create a reusable smoke test suite for example-project with primary and client ISO slots. I will bind the builds later.Create a smoke-login scenario for my app at https://my-app.vercel.app, run it in a tester VM, and verify the dashboard loads. I'll give you the password and 2FA seed at run time.Security Notes
- Use API keys only with clients you trust.
- Revoke old keys from console when you rotate machines or leave project.
- Prefer approval-required tool permissions for actions that create builds, start VMs, change infrastructure.
- Do not paste OpenFactory API keys into prompts, tickets, public repositories, shared documents.
Troubleshooting
Tools Do Not Appear
Restart MCP client and confirm server URL exactly:
https://console.openfactory.tech/mcp-stream/mcpIf client configured with retired /mcp/sse URL it will get 410 Gone: change URL to one above; nothing else needs to change.
Authentication Fails
Refresh this page and copy generated configuration again. Signed-in users should use generated Authorization header. Guest users should use generated X-Guest-Id header from copy-paste config above.
Build or VM Actions Fail
Check OpenFactory plan, organization permissions, build status. Some actions require completed build, persistent VM entitlement, or Enterprise permissions.
Transport Errors
Update MCP client if it does not support Streamable HTTP. If you cannot update it, switch to HTTP+SSE compatibility endpoint.