Every AI agent platform wants to call your business’s capabilities — and every one of them wants it shaped slightly differently. ChatGPT, Claude, Gemini, whatever ships next: each is a separate integration project, hand-written, drifting out of sync with the API underneath the moment it changes.
Archstone exists so nobody hand-writes that code. You describe what your business can do, once, in business terms. Archstone compiles that into tools an agent can discover and call — MCP today, other protocols as they arrive.
Not a server. A compiler.
Writing a single MCP server by hand is an afternoon’s work. The problem is the fifth one — and the sixth, and the one after your API changes underneath all of them at once.
Archstone is not an MCP server. It is a compiler that, in its first release, generates one. The source is twelve lines of business YAML: a capability, its inputs, its effect (read, write, or irreversible — the one distinction no OpenAPI document ever states, and the one Archstone always asks for rather than guesses).
archstone init can start from an OpenAPI document you already have. It reads the spec, asks the questions the document can’t answer, runs the real compiler over what it drafted, and writes nothing at all if that doesn’t compile.
See it work
A capability compiled by Archstone runs live at demo.archstone.dev. Point Claude at it — Settings → Connectors → Add custom connector — and ask about a trip: a destination, dates, a budget. No install, works on the free tier.
The backend behind it is a plain HTTP service you can curl directly, deterministic, so the shape an agent sees is never a mystery.
Who’s running it
ArtVinci, a custom-framing business, answers customer questions today through a capability Archstone compiled from its own real catalog and live pricing backend — not a demo, production traffic.
Licensing
Open source, Apache-2.0, published to npm — no manual integration step for anyone who adopts it.
Status
Actively developed, with a working compiler, CLI, and demo deployment. The commercial side — an operator console for teams that need audit trails and licensing on top of the open core — lives in a separate product.