SYNTHOS
Your vault is private. Until you make it a product.
FORGE is the SynthOS surface that turns a private knowledge vault into a live MCP server any agent can call — or a one-line CLI you run locally. Read-only by default. Token-gated. Pulled in one click. Nothing is shared until you act.
macOS 15+ · Apple silicon · bring your own keys
HOW IT WORKS
The forge starts cold — nothing shared, nothing listening, no address in the world. You decide what changes that.
Forge it into a live MCP server any agent can call, or a one-line CLI you run locally. You stay in control — every endpoint is scoped, and you can pull it in one click.
A faithful recreation of the Forge surface in SynthOS. Nothing is published — the real forge runs on your Mac.
STEP 1
Choose a vault. By default the forge offers it read-only — a fixed set of ten read tools: reading, listing, searching, and following links through your notes. Nothing that writes. The exact list is on screen before you commit, and you can narrow it further.
The cold forge. The card itself says it: “This vault is private.”
STEP 2
Name it. Press the button. The forge runs three beats — Mint token → Dial relay → Live — and the ring ignites. That glow isn’t an animation for its own sake: it loops only while something of yours is genuinely live in the world.
Cold forge: nothing shared. Glowing forge: you have a product in the world.
STEP 3
You’re holding the artifacts: a live URL with a pulsing status dot, your token (masked, one click copies the real value), and an install snippet for the receiving side. Copy the address, copy the token, hand them to whoever — or whatever — you trust.
<name> is forged. MCP · scoped · revocable.
Change your mind? Pull it. The token dies, the address stops resolving, the card leaves your shelf. One click, immediately, no support ticket.
For the skeptical: it’s a real MCP server. The scope is enforced at the endpoint itself — a caller can’t list, let alone call, anything outside the allow-list. The status light is computed from live signals on every render; there is no cached “online.” And live endpoints survive an app relaunch on their own.
Forge your first vault — download SynthOS →WHAT YOU CAN FORGE
An MCP. A live server any agent can call at an address — Claude, ChatGPT, Cursor, your own fleet. Whoever holds the address and the token gets exactly the tools you scoped. Nothing more is even visible.
A CLI. A one-line bundle that lives on a machine instead of at an address. Same vault, same scope rules — for your own toolchain, a script, or a hand-off that should never touch the network.
Same forge, same permissions sheet, same one-click revoke. You can do both from the same vault.
A WAY TO USE IT · BUILD SOLO
Your vault already holds the truth about your product — the decisions, the docs, the why behind every change. Forge it read-only and every agent you run anywhere gets the same source of truth: the coding agent checks the decision log before it refactors; the support draft quotes the real docs, not a guess. One brain, callable from every tool you already use.
A WAY TO USE IT · RUN CLIENTS
Every client engagement is its own project with its own vault. Forge a scoped endpoint per client and hand over the address and the token: their agents query the research, the status, the work — live, instead of waiting on your Friday email. The engagement ends, you pull it, the address dies. Access becomes part of the retainer.
A WAY TO USE IT · SHIP CONTENT
The style guide, the banned words, what actually worked last quarter — your taste lives in a vault. Forge it, and every writing agent you or your client runs can consult it before drafting. One source of voice every tool reads from, instead of a PDF nobody opens.
If it lives in a vault, it can be forged. If it’s forged, it can be pulled.
THE SHELF
Every product you forge lands on the shelf: a card with a name, a kind, and a status light. This is your storefront — small on purpose, true on purpose.
The light tells the truth. Green and pulsing only while the endpoint is genuinely serving. Offline is offline. Reconnecting is reconnecting. Each card’s status is computed from live signals every time you look — never stored, never stale, never flattering.
The dash is deliberate. Next to the lights sits a quiet pill: “— calls today.” That dash is not a bug. We don’t show numbers we don’t measure — per-call metering is on the roadmap, and until it ships, the pill stays honest.
Everything is one tap deep. Open a card for the full picture: the address, the masked token, the install snippet, the complete tool list — and the two deliberate actions: Edit permissions and Pull it.
Your products. Your tokens. Yours to pull.
MAKE IT EARN
Honest version first: SynthOS doesn’t move money for you yet. Here is exactly where the line sits.
A forged endpoint is already a product with a gate. The token is the key, and you hold every copy. Hand it to a client on retainer. Fold it into a paid engagement. Pull it the day the contract ends — access dies with it, immediately. How you invoice is your business; FORGE makes the access part real: forge, share, gate by token, revoke.
No dates we don’t control. Each of these ships when it’s real, and it will be labeled shipped here when it is — not before.
Forging early? The first publishers help set the terms — the pricing mechanics, the split, what a directory should honor. Join the founding-publisher list and we’ll build it with you.
An email, not a contract. We write back when there’s something real to decide.
TRUST & CONTROL
Scoped by default. A new forge is read-only — a fixed ten-tool read surface over the vault you chose. The allow-list is explicit and on screen. A remote caller can’t see, let alone call, anything outside it.
Token-gated. No token, no answer. The token stays masked in the app; only you copy it, and only you decide who holds it.
Revocable in one click. Pull it, and the token dies, the address stops resolving, the product leaves your shelf. There is no “pending deactivation.”
A status light that can’t flatter you. Green and pulsing only while the endpoint genuinely serves. Offline and reconnecting are computed from live signals, never cached — if the light says live, it’s live.
Local-first. The vault stays on your Mac. Calls are served from your machine; nothing is uploaded to anyone’s cloud, and cold forge means nothing is shared at all. The honest corollary: your Mac is the server — when it’s off, your endpoint is offline, and the light says so.
Everything above is enforced in the product today. Nothing in this section is a promise.
QUESTIONS
Only what’s on its allow-list. A new forge defaults to read-only: a fixed set of ten read tools — reading, listing, searching, and following links through the vault you chose. Nothing that writes. The full list is visible before you forge and any time after, and you can narrow it in the permissions sheet.
Anyone holding both the address and the token — which means: the people you gave them to. Nothing is listed publicly, there’s no directory, and the endpoint doesn’t exist at all until you forge it.
Yes. Open the product, edit its permissions, and the new scope applies from the endpoint’s next connection. If access needs to be gone now, that’s what Pull it is for — revoke is immediate.
No. FORGE is local-first: your Mac serves the calls, so it needs to be on, with SynthOS running. When it isn’t, the status light says offline — it never pretends. Live endpoints come back on their own when you reopen the app. Always-on hosting is on the roadmap.
You can gate it today: the token is the key, and you decide who holds one — hand it to paying clients, pull it when they stop paying. Billing inside the product (per-call metering, prices, payouts) is roadmap, and it’s labeled that way above.
Forge an MCP when something should be callable at an address: a client’s agents, your own agents in other tools, anything that speaks MCP. Forge a CLI when access should stay on a machine — a one-line bundle, no address, no network. Same vault, same scope rules, and you can do both.
Nothing is shared, ever, until you say so. When you do, it’s two clicks — and one click back.
SynthOS — the AI operating system for a company of one. Hire no one. Run everything.