An MCP gateway is a single endpoint an AI client connects to in order to call a defined set of tools. A brand gateway serves the brand record: an agent points a client at one address, passes a token, and reads the brand instead of guessing it.
Why it matters
Agents are only as good as what they can reach. Point a general assistant at a brand and it works from whatever it absorbed in training, which is usually a competitor's language and a product list from two years ago.
MCP, the Model Context Protocol, is how AI clients call tools in a standard way. A gateway built on it lets a brand hand every agent one address instead of asking each developer to scrape a site or paste in a briefing document.
The useful ones are narrow. A gateway that returns a brand's own facts is a different thing from a connector that routes an agent into a thousand generic app actions.
How Jinn treats it
The Jinn gateway is a single read-only MCP endpoint. Point Claude Code, Cursor, or any MCP client at it with a bearer token, and an agent can read the brand, its voice, positioning, messaging, product, and design system, before it generates a word.
Reading is the whole design. The tools wrap contracts the Jinn products already run on, so an agent asking for the record hits the same data path a person in the product does. Nothing is rebuilt as a demo layer.
The endpoint, the tool reference, and the auth model are documented publicly. See it
Related terms
One address, and the agent stops guessing.
A read-only endpoint, a bearer token, and the brand answers for itself. Read the gateway docs.