Praecise Harness v1.1.0 Get started

Documentation · Running

Handing it to someone else

An app is finished when someone else can run it. praecise package writes a directory that installs and starts like anything else on npm:

praecise package ./dist
cd dist && npm install && npx my-app

What comes out is your own files, a launcher, and mcp.json — the tool surface, written down. Nothing is bundled or compiled, because the folder already is the app. Keeping the surface in a file means a rename shows up as a diff someone can review rather than as a break a caller discovers at run time.

It also comes out importable, for a caller that would rather write code than read a list of tools:

ts
import app from "my-app";

const answer = await app.support({ input: "where is order 4021?" });

That is the same app under the same rules — api.d.ts is a line per tool where mcp.json is a schema per tool, which matters when the reader is a model paying for every one of them.

The same folder also runs in place. praecise mcp serves it on stdin and stdout for a client that launches it as a subprocess, and praecise dev serves it over HTTP for a browser and for anything already speaking the protocol.

Edit this page on GitHub · Read it as Markdown

    Type to search. Arrow keys move, Enter opens.