We have our own MCP The LOOM Protocol
3 servers. Point Claude, Cursor or your own agent at one and the studio’s tools show up inside it — a brand that answers back, a content machine you can call, and a 3D room you can ask for in a sentence.
Private beta Keys are issued by hand. There is no signup on this page, no console and no free tier — you ask, a person reads it, and if it fits you get the host and a key back.
— Plain language
Nothing below is about LOOM. It is what the protocol is, so the three servers after it are readable without a glossary.
01
MCP stands for Model Context Protocol. It is a common way for an AI client — Claude, Cursor, or an agent your own team runs — to plug into a system that sits outside it. Before a protocol like this, connecting an assistant to anything meant writing a bespoke integration per assistant.
02
A server publishes a small set of named tools. The assistant can see what each one is for, decide when to call it, pass it arguments and read what comes back — so “make me the January grid” becomes a real call against a real system rather than a paragraph of plausible text.
03
You point your client at the server’s address and give it a key. From then on the tools appear inside the assistant you already use — nothing is installed, nothing moves to a new interface, and the work happens where your team is already working.
— The servers
Every tool is listed with what it does — no tooltips, nothing behind a hover. The address each server answers on is shown with the host struck out, because the host and the key are the two things access actually buys.
Brand context server
The brand as data, not a style guide to remind it of — tokens, tone and approved lockups, read live. A model that drifts gets corrected by the source.
Tools it exposes 4
brand.tokensbrand.voiceasset.findcopy.check
Content production server
The Machine, exposed as tools — plan, draft, render, queue, from wherever you already sit. Nothing ships until an editor releases it.
Tools it exposes 4
month.planpost.draftpost.renderqueue.release
3D & AR server
A photo goes in, a mesh comes out — staged in a room the customer can walk around on their phone. Ask for it in a sentence instead of booking a render.
Tools it exposes 4
mesh.from_photoroom.stagear.linkcatalogue.sync— Access
There is no self-serve path and there is not going to be one while this is a beta. Tell us who you are and what you would wire it to; if it fits, the host and the key come back by hand.
Both open a message you can read before you send it. Nothing on this page posts anywhere — this site has no backend, and it is not going to pretend it does.
Amman × Sarajevo
— Contact
Tell the machine what you are making. A human answers — fast, and in your language.
Amman × Sarajevo
