How to use Ovenfo

From zero to your first instantiated project: account, AI agent integration, project, infrastructure, modules and example prompts.

1. Create your account

Your Ovenfo account is a single one for every product and is created in the accounts portal.

  1. Open the sign-up link and fill in e-mail, first name, last name and password, or use Google.
  2. If you sign up with e-mail you will get a verification message. The account is activated when you open the link.
  3. The first time you sign in choose whether you will use Ovenfo as an individual or as a company, and accept the system terms.
  4. Ovenfo takes you back to the Builder application with the Free plan active: 5 projects, no card.

2. Integrate it with your AI agent

The Ovenfo connector is the single entry point for your agent. When you add it you sign in and authorize access on an Ovenfo page (OAuth): the agent never receives your password or a platform credential, and you can revoke access at any time. Pick your agent:

Ovenfo connector URL
https://app.builder.ovenfo.com/mcp
Claude Code
  1. Run the command in your terminal.
  2. Inside Claude Code open the connection manager with /mcp, pick ovenfo and select Authenticate.
  3. Sign in to Ovenfo in the browser and click Allow.
Terminal
claude mcp add --transport http ovenfo https://app.builder.ovenfo.com/mcp
Optional: available in all your projects
claude mcp add --transport http --scope user ovenfo https://app.builder.ovenfo.com/mcp

If the browser does not open, copy the URL that Claude Code shows. To revoke access use Clear authentication.

Official documentation: Claude Code: connectors documentation

Claude Desktop and claude.ai
  1. Go to Customize > Connectors, click + Add and choose Add custom connector.
  2. Enter the name Ovenfo, paste the connector URL and click Continue.
  3. Leave authentication on OAuth, click Add and then Connect to sign in to Ovenfo.
  4. In a conversation, open + > Connectors and turn Ovenfo on.
Connector URL
https://app.builder.ovenfo.com/mcp

Remote connectors are set up from your Claude account and need the server to be reachable from the internet. On Team and Enterprise an organization owner adds it first.

Official documentation: Claude: custom connectors

ChatGPT
  1. Open Plugins (chatgpt.com/plugins), click + and choose the option to add a custom server.
  2. Enter the name Ovenfo and paste the connector URL under Connection.
  3. Under Authentication choose OAuth, accept the warning and click Create as a plugin.
  4. Install the plugin you created and sign in to Ovenfo when prompted.
Connector URL
https://app.builder.ovenfo.com/mcp

OpenAI has renamed these screens several times; availability depends on your plan and workspace permissions.

Official documentation: OpenAI: custom servers · OpenAI Help: custom connectors in ChatGPT

Cursor
  1. Add Ovenfo to ~/.cursor/mcp.json (global) or to .cursor/mcp.json inside your project.
  2. Cursor detects that it needs OAuth and opens your browser so you can sign in to Ovenfo.
~/.cursor/mcp.json
{
  "mcpServers": {
    "ovenfo": {
      "url": "https://app.builder.ovenfo.com/mcp"
    }
  }
}

Cursor registers its own OAuth client automatically; you need no prior credentials.

Official documentation: Cursor: connectors documentation

VS Code and Copilot
  1. Create .vscode/mcp.json in your workspace (or use the add-server command of the Command Palette, choose HTTP and paste the URL).
  2. Start it from the file and complete the Ovenfo sign-in in your browser. Ovenfo becomes available to Copilot in agent mode.
.vscode/mcp.json
{
  "servers": {
    "ovenfo": {
      "type": "http",
      "url": "https://app.builder.ovenfo.com/mcp"
    }
  }
}

VS Code uses the servers key and "type": "http", unlike mcpServers in other clients.

Official documentation: VS Code: connectors configuration

Grok (xAI)
  1. Grok app: open grok.com/connectors, click New Connector, choose Custom, paste the connector URL and complete the authentication.
  2. Grok Build (CLI): run the command; with OAuth the browser opens on first use.
Grok Build (terminal)
grok mcp add --transport http ovenfo https://app.builder.ovenfo.com/mcp

xAI’s documentation does not say whether the app’s custom connectors support OAuth with dynamic registration: if sign-in fails, use another agent or write to social@ovenfo.com.

Official documentation: xAI: Connectors · xAI: Grok Build

Instructions checked against each provider’s official documentation on 5 November 2026. Interfaces change often: if a menu does not match, follow the linked documentation.

3. Instantiate your first project

With Ovenfo connected, ask for the project in plain language (examples in section 6).

What happens

  • Your agent picks the Ovenfo tool and fills in the details; if the company alias or the project name is missing, it asks you.
  • Instantiating a project registers something in your name, so the agent asks you to confirm before running it.
  • The project is registered under your company and user, and counts against your plan limit.
  • Repeating the same alias does not create a second project: it reconciles the existing one and regenerates the code.

What you receive

  • A download link valid for 24 hours with a ZIP of the repositories: API, shared libraries, web Shell, administration module, database, cache and documentation, plus the workspace scripts, AGENTS.md and its .env.
  • Extract it into the folder where you keep your repositories, keeping each repository folder at the root, and open it in your IDE.
  • The link is a secret: anyone who has it can download the file until it expires. Do not paste it in tickets or chats.

Plan limits

  • The Free plan allows 5 projects. The Builder panel shows how many you have used.
  • At the limit, the next new project is rejected with a plan-limit message. Modules and containers do not register new projects.
  • For more projects change plan from the Builder panel or see the pricing: https://builder.ovenfo.com/en/pricing/

4. Instantiate the infrastructure

When the project is registered, Ovenfo starts provisioning its cloud infrastructure.

  • The infrastructure is instantiated on AWS. Google Cloud and Azure arrive in Phase 2 (roadmap). To pick the environment and your company’s cloud configuration, use the Builder panel.
  • The Deployments history in the panel shows every provisioning run of your projects with its status.
  • Project files can be stored on local disk or on AWS, independently of where the application is deployed. Storage on Azure and Google Cloud arrives in Phase 2.
  • The infrastructure is container-based on open standards; you can also take the code to your own servers.

5. Instantiate modules

A project grows by business modules.

  • Ask your agent for a new module (for example, Inventory) for your project: API, Angular screen or both, with their own ports and storage.
  • The result lists what is left to wire: the Shell remote and route, the workspace files and the menu in the database.
  • Downloading modules from the ovnModule catalogue to integrate them into your project arrives in Phase 2 (roadmap).
  • Module and landing page catalogues available to your agents are on the roadmap and not available yet.

6. Example prompts

Copy and adapt them. Replace ACME and Ventas with your company alias and your project name.

Check the connection

Prompt 1
List the Ovenfo tools you have available and explain in one line what each one does.

Instantiate a new project

Prompt 2
Create a new Ovenfo project: company ACME, project Ventas, PostgreSQL database, scripts for Linux and files on AWS. Confirm the details with me before creating it.

Project with regional data

Prompt 3
Create the ACME / Ventas project on PostgreSQL, scripts for Windows, files on AWS, with initial data only for Peru, in soles and dollars.

Add a complete module

Prompt 4
Add an Inventory module (backend and web) to the ACME Ventas project.

Module with its own ports

Prompt 5
Add a Census module to this project; use ports 8820 and 4220 and store the files on AWS.

Database container

Prompt 6
I need a PostgreSQL container for ACME Ventas, Mexico only, in Spanish and English, with pesos and dollars (the peso as default).

Cache container

Prompt 7
I need a Redis container for ACME Ventas on port 6390.

Tell the agent which folder to extract the ZIP into. Pick free ports if you add several modules or containers, because the defaults clash with each other.

7. Next steps

  • Open the project in your IDE and let your agent read AGENTS.md and the specifications before asking for changes.
  • Add business modules with the same prompt flow and review your deployments in the panel.
  • Check your plan usage in the Builder panel and change plan when you need to.
  • If you have a legacy system, ask your agent to analyze it part by part: a person reviews and approves the proposals in the application.
  • See the roadmap to know what is coming.

Frequently asked questions

Is it free?
Yes: the Free plan includes 5 projects and needs no card. Paid plans are on the pricing page.
Who owns the generated code?
You do. It is standard code you can host, change and maintain without depending on Ovenfo.
Which agents work?
Claude, ChatGPT, Cursor, Copilot in VS Code and Grok, among others: any agent that supports remote HTTP connectors with OAuth.
Does my agent know my password?
No. You sign in and authorize on an Ovenfo page; the agent receives a token that only works for Ovenfo and you can revoke it at any time.
What if I reach my plan limit?
New projects are rejected until you change plan; your existing projects keep working.
Where do I get help?
Write to social@ovenfo.com or use the contact form on ovenfo.com.