MCP
Your brand, its rules, its context and your research, inside your AI tools. Nobody pastes the brand book again.
Monobase is an MCP server for your brand: your AI tools read your Brand System and design system. Once an owner allows it, they write to the Brand System too.
Lumo wants its own voice here, so I’ll read its Brand System over MCP before writing: the Tone of voice first, then the Positioning.
Lumo Citrus is out today. Real fruit, a little sour, summer in a can. Try it cold.
Works with
- Claude A custom connector
- ChatGPT A custom connector in developer mode
- Gemini Gemini CLI and Gemini Enterprise
- Le Chat Mistral’s assistant: a custom MCP connector
- Figma Make A custom MCP connector
- v0 An MCP connection
- Claude Code A remote MCP server
- Codex A remote MCP server
- GitHub Copilot Agent mode in VS Code
- Cursor A remote MCP server
- Windsurf A remote MCP server
- Zed A remote MCP server
Where it works
Your team’s AI tools, on brand.
- Summer in a can. Real fruit, a little sour.
- Cold, bright and squeezed, not flavoured.
- Weekend plans: one can, one friend, one table outside.
| color.action.primary | {citrus.500} → #F2B33D | color | ||
| color.action.primary-hover | {citrus.600} → #DB9A22 | color | ||
| color.action.on-primary | {night.900} → #1F2A3C | color |
- {
- "storeFinder": {
- "title": "Where to find Lumo",
- "search": "City or postcode",
- "cta": "Find a store",
- "secondary": "Try it cold",
- "browse": "See the flavours",
- "empty": "No store nearby yet."
- },
- "storeCard": {
- "open": "Open now",
- "closed": "Opens at {time}",
- "directions": "Directions"
- },
- "filters": {
- "cold": "Sold cold",
- "zero": "Has Lumo Zero"
- }
- }
- <mjml>
- <mj-head>
- <mj-attributes>
- <mj-all font-family="Lumo Sans" />
- </mj-attributes>
- </mj-head>
- <mj-body>
- <!-- hero -->
- <mj-section padding="24px 0">
- <mj-column>
- <mj-text padding="0 16px">
- Summer in a can.
- </mj-text>
- <mj-button padding="16px">
- Find a store
- </mj-button>
- </mj-column>
- </mj-section>
- </mj-body>
- </mjml>
Global · spacing, px
How to connect
Connect the MCP server once. Ask in any chat.
-
Paste your workspace’s address into your AI tool.
-
Sign in to Monobase and authorise once.
-
Ask, and it reads your brand before answering.
Reads your brand.Writes only if you allow it.
-
What it reads. Your Brand System and design system, nothing else.
-
Read-only by default. Every member’s tools only read. Writing stays off until an owner switches it on.
-
One workspace. Each connection reads one workspace, with its own address.
-
Your sign-in rules. Two-factor and SSO apply. Your profile lists every tool.
-
Your own MCP servers. Monobase’s agents use MCP servers you add, with a token or OAuth.
Questions about the brand MCP server
What is the Monobase MCP server?
The Monobase MCP server is a remote MCP server for your Monobase workspace. AI tools that support remote MCP, such as Claude, ChatGPT, Cursor and GitHub Copilot, connect to it and read your Brand System and design system, read-only by default.
How do I give Claude our brand guidelines?
Connect Monobase instead of pasting a PDF. Copy your workspace’s MCP address in Monobase, add it in Claude as a custom connector, then sign in and authorise once. Claude reads the documents it needs when you ask. More in our guide to AI brand guidelines.
Which AI tools work with it?
Any AI tool that connects to a remote MCP server and signs in with OAuth, such as Claude, ChatGPT, Cursor and GitHub Copilot in VS Code. Monobase is not a certified integration of any one vendor; the names and logos are trademarks of their owners.
What can the AI tool read?
Your Brand System documents and your design system, nothing else: not visual identity, templates, media, campaigns, the calendar or signals. One connection reads one workspace.
Can the AI tool change anything in Monobase?
Only if you allow it. By default its tools only read, and Monobase answers them from your workspace without calling a model. When a workspace owner switches on Write over MCP, owners and admins can also work on the Brand System from their AI tool: import Markdown documents, add sub-brands, divisions and products, update audiences, and approve, rename or move documents. Everyone else keeps reading. An imported document stays a draft unless the tool asks to approve it, the old version stays in the history, and every change lands in the audit log. The design system, templates, media and campaigns stay out of reach.
Does it read drafts?
Once a document is approved, AI tools read that version; new edits wait in Monobase until the next approval. A document nobody has approved yet is read as its live draft.
Does it work when our workspace requires two-factor or SSO?
Yes. The tool gets in only after you verify, with a code where two-factor authentication is required or through your identity provider where SSO is enforced. The connection then lasts up to 30 days before you reconnect it.
What else does Monobase connect to?
Your own MCP servers, for Monobase’s agents, and the tools your team already uses: Monobase reads briefs from Google Drive, Notion and ClickUp, takes your design system from Figma, publishes approved posts and reads your results. Every one is on the integrations page.
