Braandly is built to connect to the rest of your stack. You can read and write your brand data from your own code, let an AI assistant work in your workspace, pull brand assets straight into your design tools, or save inspiration as you browse. This article explains the options and points you to the right guide for each.
Ways to connect
- The public API. A REST API for reading and writing brands, workspaces, projects, tasks, docs, brand guidelines, and Brinks, plus the public catalog of palettes, fonts, and gradients. Use it when you are writing code or wiring up an automation. See Use the Braandly public API.
- The MCP server. A hosted Model Context Protocol server that turns the API into tools an AI assistant can use. Connect Claude, Claude Code, Cursor, ChatGPT, and other AI clients and ask them to manage your tasks, docs, and brands in plain language. Many clients sign in with Braandly directly; the rest use an API key. See Guide to Model Context Protocol (MCP) in Braandly.
- The Figma plugin. Brings your brand colors, fonts, logos, and assets into Figma so your designs stay on-brand without leaving the canvas. Search your brands, then click or drag assets in. Install it from the Figma community and connect it with an API key.
- The browser extension. Saves colors, fonts, and inspiration from any site straight into your workspace, and puts your brand assets a click away while you browse. Available for Chrome, Firefox, and Edge (and their Chromium and Gecko cousins, like Brave, Opera, and Zen). It connects with an API key.
More design and site-building tools are on the way, including Canva, WordPress, Elementor, and Adobe. You can see the full, current list on the integrations page.
Which one should I use?
- Writing a script, a backend integration, or an automation? Use the public API.
- Want an AI assistant to do the work in conversation? Use the MCP server.
- Designing in Figma? Use the Figma plugin to keep your work on-brand.
- Collecting colors, fonts, and inspiration while you browse? Use the browser extension.
The common foundation: API keys
Most integrations authenticate with a Braandly API key. A key is tied to your account, carries a set of scopes that decide what it can read and write, and only works in workspaces you belong to. Create one before you set up the public API, the Figma plugin, or the browser extension. See Create and manage Braandly API keys.
The MCP server can also authorize through sign-in (OAuth) for clients that support it, so you do not have to paste a key. Either way, the same scopes and workspace roles apply.
Access follows your workspace role. A guest key is read-only. To create or change anything through an integration, you need a workspace role of member or higher, and a key with the matching write scope.