Public by default
Work you do on the public engine lands in a public, forkable commons that anyone can read.
Keeping work private currently means running the engine yourself — see how to host it.
how to connect · entry one
Connect your chatbot.
One URL turns any MCP-capable chatbot into a control station for Tiny: it can browse the public commons, design workflows with you, and start real runs. No account, no install — just paste the address below into your assistant's connector settings.
is the door open? read it yourself
reading the endpoint…
— you're reading my pulse through the same door you're about to walk through.
before you paste · two honest things
Where your work lives.
Yours to take
Universes and the commons are plain files in an open-source store, so you can export your work at any time.
The engine's code is MIT-licensed on GitHub ↗.
— no surprises after the paste. This is the deal up front.
entry two · the two simple steps
Add the URL, then talk.
Connecting is two steps in any client: register the connector, then start a chat with it enabled. The exact menu path differs per chatbot — here are the two that work today.
Best path if Claude is where you already ask for help. Free, Pro, Max, Team, and Enterprise can add a custom remote connector, within plan limits.
- 1Open Settings → Connectors.
- 2Choose Add custom connector.
- 3Paste
tinyassets.io/mcpand approve it. - 4Start a chat with the connector enabled and send a starter prompt below.
The custom-URL path is the current one. A Claude directory listing is still pending, so this page doesn't claim directory acceptance.
The same URL is a standard remote MCP server, so any MCP-capable client connects the same way — paste it into the connector / remote MCP field.
- 1Open your client's connectors / MCP servers setting.
- 2Add
tinyassets.io/mcpas a Streamable HTTP / remote MCP server. - 3Enable it in a chat and send a starter prompt below.
So which should you use today? The reliable path is Claude.ai — or any client that supports custom MCP connectors. On ChatGPT specifically, custom connectors require a paid plan with developer mode turned on, and availability still varies by workspace and region. We track where that actually stands here: current status on Workflow on GitHub ↗.
entry three · what to say first
Bring a first sentence.
— connected and not sure what to ask? Here are six openers, one per kind of visitor. Each works today through my universe, goals, and commons tools. Swap the bracketed bits for your own.
- The researcher orient first
- The maker build something
- The novelist long project
- The shop owner commerce, carefully
- The curious see the whole thing
- The contributor file friction
Wondering what a "goal" or the "commons" is? Open the live goals board — it reads the real list straight from the engine.
entry four · other ways in
Or run the engine yourself.
Tiny is the public face of Workflow, an open-source engine. You don't need to host anything to use the connector above — but if you'd rather run it locally or read the code, both paths are real.
Clone the repo
Read the engine, the loop, and every workflow definition. It's all public.
git clone https://github.com/Jonnyton/Workflow.gitRun it locally
Python 3.11+. Install in editable mode and you have a local daemon to work against.
pip install -e .