A directory of software your agent can adapt or operate

Some software you pull down and change to fit your business. Some you point your agent at and let it work. mothermachine lists both, and every listing says which it is, how much is yours to change, and where your agent's reach ends.

Adaptable and operable

A listing is adaptable when its source is public and there is a named surface to change: env vars, config files, prompt files. The effort badge says how much work that is. A listing is operable when an agent can drive it through an interface: an MCP server, an API, an SDK, config files, or as a last resort the screen. Many listings are one or the other. Some, like an open-source editor with its own MCP server, are both.

Where the agent's reach ends

Every operable listing enumerates the jobs the software does and marks each one reachable or not through the stated interface. The jobs an agent can't do are shown as prominently as the ones it can, because that boundary is the thing you need to know before you build a workflow around it.

How the code was written

Whether a listing was vibe-coded or written by hand is recorded as its own field. It is never a condition of being listed and never used to sort the directory.

How listings are classified

• Form factor is what the thing is: a web app, a CLI, a skill, an MCP server, an agent. Filter on this first.
• Execution model is whether a model runs at runtime. Deterministic apps don't call one. AI inferential apps do, open-endedly. Hybrid apps run fixed orchestration with a model doing bounded work inside it — most skills and agents live here.
• Code stack is language, framework, database, host. Read from the repo's manifests.
• Model stack exists only for AI and hybrid apps: provider, model, the keys you'll need, where the prompts live.
• Editions are the ways it is offered: free or priced, open or closed, each with its own way to get it. Open-core software is one listing with a free open edition and a paid one.
• Customization is the builder's own account of what to edit to make an adaptable listing yours, and how much work that is.
• Operability is how an agent drives an operable listing: native, official, wrapped, config, or gui. Wrapped listings name one recommended wrapper.
• Reach is the list of jobs an agent can and cannot do through that interface.

Free and paid

Anyone can list software that has a free or open edition. The repo's license governs; we're an index. Paid editions sold through mothermachine require a verified builder. Both can carry the owner-verified mark.

For agents

Point an agent at this site and it can find an app for you. Everything on a listing page is also published as JSON with the same vocabulary: api/listings.json for the whole directory, api/vocabulary.json for what each value means, and llms.txt for the short version. Each listing carries a "use it when" list written in plain words, and every classified field says whether it was detected or confirmed, so an agent can tell a guess from a fact.

Detected, then confirmed

We fill listings from the repo rather than from a form, because a parser is more consistent than a tired builder. Each field remembers whether it was detected or confirmed by the owner, and we show that on the page. If a listing is wrong, the owner can claim it and fix it.