Developer Tools
Integrate AI-powered OS building into your workflows. Connect Claude Code, build custom automations, or embed OpenFactory in your applications.
AI Integration
OpenFactory exposes a full MCP server that AI assistants like Claude can use to build and manage OS images on your behalf.
Connect Claude Code directly to OpenFactory. Ask Claude to build custom Linux images, run tests, or manage your fleet - no API key required.
"Build me an Ubuntu server with Docker and SSH enabled"
Build your own AI agents that use OpenFactory. Create automated pipelines, CI/CD integrations, or custom tooling.
Use the Claude Agent SDK with OpenFactory tools
1. Add MCP Server
Run Claude Code with the OpenFactory MCP server:
claude --mcp-config openfactory.mcp.json2. Create config file (optional)
Or add it to your project's .mcp.json:
{
"mcpServers": {
"openfactory": {
"url": "https://api.openfactory.tech/mcp/sse"
}
}
}No API key needed - your session is linked to your IP for seamless browser sync.
3. Start Building
Ask Claude to build an OS image. Builds appear in both Claude Code and the OpenFactory web UI automatically.
For persistent account linking or team use, generate an API key from your settings page:
{
"mcpServers": {
"openfactory": {
"url": "https://api.openfactory.tech/mcp/sse",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Available Tools
These tools are available to AI assistants connected via MCP. No API key required - your session is automatically linked to your IP address.
list_buildsList your builds with status and basic infoget_buildGet full details including recipe and configcreate_buildCreate a new build from a recipe JSONget_build_statusGet current build stage and progressget_iso_download_urlGet download URL for completed buildsretry_buildRetry a failed build with same recipelist_recipesBrowse pre-built recipe templatesget_recipeGet full recipe details and configvalidate_recipeValidate a recipe without buildingcreate_recipe_from_templateCustomize a template for your needsrun_testsRun tests on a built ISOget_test_resultsGet detailed test results and logslist_test_runsList test runs for your buildslist_vmsList running VMs from your buildscreate_vmCreate a VM from a built ISOstart_vm / stop_vmControl VM power stateExamples
Ask Claude to create a custom OS with natural language:
"Create a Debian server image for a web application. I need nginx, Node.js 20, and PostgreSQL. Enable SSH on port 2222 and set up a static IP at 192.168.1.100."
Claude will use create_build with a complete recipe
Use the MCP tools in your automation pipelines:
# 1. Create build from recipe
build = await create_build(recipe={
"name": "web-server-v2",
"base_image": "ubuntu-noble",
"features": ["ssh", "nginx", "docker"],
"packages": ["nodejs", "npm"]
})
# 2. Wait for build completion
while status != "built":
status = await get_build_status(build_id)
await sleep(30)
# 3. Run tests
test_run = await run_tests(build_id)
# 4. Check results
results = await get_test_results(run_id)
if results.all_passed:
deploy(build_id)Start from proven templates and customize:
"Show me healthcare recipes with GxP compliance"
"Take the AI workstation recipe and add ROS 2 support"
Claude will use list_recipes and create_recipe_from_template
Authentication
API keys are optional. Without one, your builds are linked to your IP address and shared between Claude Code and the browser. Use an API key for persistent account linking or team collaboration.
Without API key: builds sync between Claude Code and browser automatically.
Keys are hashed on creation. We never store the raw key.
Delete keys anytime to immediately revoke access.
Create an account and generate your first API key to start building with AI.