Archstone MCP server

Archstone — connect your business to every AI

A compiler for AI capabilities. You describe what your business can do, once, in business terms. Archstone compiles that into tools an AI agent can discover and call — MCP today, other protocols as they arrive. Nobody hand-writes integration code.

Open source, Apache-2.0.

See it work — 60 seconds, nothing to install

A capability compiled by Archstone is running live. Point Claude at it:

https://demo.archstone.dev/mcp

Open Claude (web, desktop or mobile) → Settings (or Customize) → Connectors → Add custom connector → paste the URL. Then ask about a trip — a destination, dates, a budget. Works on Free too (one custom connector is all this needs).

Prefer a terminal:

claude mcp add --transport http archstone-tourism https://demo.archstone.dev/mcp

The backend behind it is a plain HTTP service, and you can curl it directly — the same data the agent sees, deterministic so the shape is obvious:

curl -s -X POST https://demo.archstone.dev/v1/search \
  -H "content-type: application/json" -d '{"destination":"Rome"}'

The entire integration that made this callable by an agent is 12 lines of business YAML — no HTTP, no JSON Schema, no MCP SDK. Everything else was generated.

Start from an API you already have

Point archstone init at an OpenAPI document. It reads the spec, asks you the questions no document can answer, runs the real compiler over what it drafted, and writes nothing at all if that does not compile.

archstone init openapi.yaml --out manifest --company acme --domain catalog

The one answer it never guesses is effect — read, write or irreversible is the difference between looking up a price and charging a card, and no spec says which. Where a response could honestly be read two ways, it asks rather than picking. With --probe it will also make one read-only call to your real backend and record a genuine fixture, so archstone verify has something true to replay later.

The spec in that recording is examples/demo/stays-openapi.yaml, describing the demo backend in this repository — you can run it yourself.

Who is running it

ArtVinci — a custom-framing business — answers customer questions today through a capability compiled by Archstone. Real catalog, real prices computed live by their own backend. See the case study.

Why a compiler, and not just an MCP server

Writing your first MCP server is not the hard part — it is a few hundred lines, and you can do it in an afternoon.

The work is the fifth one. ChatGPT, Gemini and whatever ships next each want the same capability shaped slightly differently, every one of them is a separate integration project, and your API keeps changing underneath all of them at once.

Archstone is not an MCP server. It is a compiler that, in its first release, generates one.

One capability definition (CDL) lowers to a target-agnostic IR; emitters consume the IR. MCP today; REST · GraphQL · SDK tomorrow. Change the protocol and you regenerate — you do not rewrite. Change the backend and the CDL and the generated tool do not move at all.

That is what zero manual integration means: not that the first server is easy, but that the maintenance disappears instead of multiplying.

How it works

capabilities.yaml   →   *.capability.yaml   →   bindings/*.binding.yaml
(what the company     (each capability:        (how one capability maps
 offers — the index)   business shape only)     to a real HTTP endpoint)

Shortened. The full README is on GitHub.