Making games with Ollama, and what that does not buy you

If your agent speaks MCP, the model behind it can be one you are running yourself. That changes where the thinking happens. It does not make Stage Engine an offline tool, and this page is mostly about that difference.

Start with the part people get wrong

The reason to search this is usually a hope: that with the model on my own machine, the whole thing runs on my own machine. That hope is wrong here and it is better to know now than after a download.

Stage Engine needs an internet connection to build with. Asset generation and world data come over the network. Those are not the model, they are separate services doing separate work, and hosting a model in Ollama does not touch them. Put a laptop on a plane with Ollama running perfectly and you still cannot build.

What does work without a connection is playing what you already built. The game runs locally on the copy of Godot bundled with the app, at your machine's framerate. That distinction — building needs the network, playing does not — is the honest version, and we are not going to add an offline mode later to make this page age better.

What running the model yourself does change

It changes who pays for tokens and where the conversation goes. If you are driving Stage Engine from an agent whose model is served by Ollama, that part of the loop is yours: your hardware, your model choice, your cost of zero beyond electricity, and the prompts staying on the machine.

It also changes your ceiling in both directions. You are not subject to somebody else's rate limits, and you are subject to your own GPU. Which of those matters more depends entirely on your machine and we are not going to pretend to know.

We are also not going to tell you which model to run. We have not benchmarked local models against each other for this and any ranking we published would be a guess dressed up as data. Try what you have.

Why a smaller model has a chance here at all

This is the genuinely interesting part. Pointed at a bare game project, a model has to invent nearly everything: what the scene means, where things belong, how terrain and water and weather are represented, what a character even is in this codebase. Every one of those inventions is a chance to be subtly wrong, and small models are worse at recovering from subtle wrongness than large ones.

Stage Engine exposes a capability layer over MCP instead. The operations are at the level a game is described in rather than the level a file is edited at. Each real capability is a body of code the model does not write from nothing and a class of failure that stops happening.

The practical consequence is that a locally hosted model is not obviously a bad idea here in the way it is when you point one at a raw engine. We are not claiming a specific model works well — that depends on your model and your machine and we have not measured it. We are saying the layer is built so that reliability comes from the tools rather than from the size of the model, and that is the reason to try.

There is no Ollama integration

To be exact: we have not built anything for Ollama, and Ollama has not built anything for us. Ollama serves models. What connects to Stage Engine is an agent, and it connects because both sides speak MCP.

So the shape is three pieces. Ollama serving the model. An MCP-capable agent using it. Stage Engine, running on Mac or Windows, with two MCP servers inside it — one for the Stage capability layer, one for assets. Popular clients should work, behaviour will vary between them, and we have not tested them all.

Get the connection details from the app and its docs rather than from a page like this. Configuration published on a marketing page goes stale quietly, and a wrong instruction costs an evening.

The rest of the work is still yours

The world is built by hand, in the builder, by a person. Terrain, water, weather, buildings, characters. No agent does that part, local model or otherwise, and it is the design rather than a gap.

You also still judge the result. You play the game and say whether it is right, and the agent goes again. Not writing the code has never meant not having an opinion about the game.

External agent access is on the paid plans — Indie at $10 a month, Pro at $50 — and the free plan does not include it. Which is worth weighing honestly against the reason you wanted a local model in the first place: if the goal was zero spend, this route does not get you there.

Questions

Does running Ollama make Stage Engine work offline?
No. Asset generation and world data still go over the network, so building needs a connection regardless of where the model runs. Playing what you built does not.
Is there an Ollama integration?
No. Stage Engine ships two MCP servers. An MCP-capable agent connects to them, and the model behind that agent can be one Ollama is serving.
Which local model should I use?
We have not benchmarked local models for this and will not rank them. Try what your machine runs comfortably.
Is this free because the model is local?
No. External MCP access is part of the paid plans, Indie at $10 a month or Pro at $50. The model being yours does not change that.
Can I use Director 1 instead?
Yes. Director 1 ships in the app, writes the GDScript into your project, and needs no connecting. For most people it is the shorter path.