makefx is a workshop for making finished media with your agent: a scroll film for a landing page, a presenter ad for a product, an art pack for a game. The agent works over MCP; every asset lands on one canvas with the recipe and the price that made it; you look, pick, drag, trim and steer.

It is being built in the open, milestone by milestone. Today you can sign in, create spaces, upload or generate assets, buy credits and connect an agent. The web app, MCP endpoint and repository CLI work with the same spaces and assets.

How it is built

One space is one canvas and one set of assets. An asset is one media file with one recipe: the model, the prompt, the settings and the references that made it. A generated recipe is written by the system and never changes; iterating means a new asset made from the old one, placed next to it. Any ready asset can be a reference for the next.

Generation is paid per asset from a prepaid balance, with the price shown before a request runs and recorded after. There is no subscription, no plan and no free tier.

Who runs it

makefx is published by Aleksei Krasnoperov. Questions, feedback and security reports go through the contact page.

How it treats your data

Accounts are created by signing in with Google; makefx keeps the name and email address Google shares and nothing else about the Google account. The privacy page lists exactly what is stored, where it lives, how long it is kept and how to have it removed, and it changes when the code does.

For agents and developers

An agent connects over MCP and acts with your consent, within the scope you grant; you can revoke that access at any time. The developers page documents the MCP endpoint, the HTTP API and the OAuth 2.1 authorization server; llms.txt says what the tools can do today and how to call them.