Bloom is an AI brand and creative studio: point it at a brand and it analyzes colors, typography and logos into a brand profile, generates a Markdown "Brand Skill" summary an agent can read, and produces on-brand images against it. Until today, none of that lived anywhere an agent could reach it without someone opening the Bloom app and copying it out by hand. That changes today.

Bloom is a live MCP integration in Cogny. Connect a single API key and Claude (or any MCP client on app.cogny.com/mcp) can read your brands, their generated Brand Skill, and your generated images in natural language.

TL;DR

Bloom is live now. Connect it with an API key from Settings → Cogny Managed MCPs.
Six tools, strictly read-only by design: bloom_get_account, bloom_list_brands, bloom_get_brand, bloom_get_brand_skill, bloom_list_images, bloom_get_image. No brand creation, editing, image generation or delete tools — this first release never writes back to your Bloom workspace.
bloom_get_brand_skill returns a brand's full generated profile (colors, typography, logo catalog) plus its Markdown summary files, with long file content capped so one call can't flood the agent's context.
Lists (bloom_list_brands, bloom_list_images) are cursor-paginated, one page per call.
A brand or image still being analyzed/generated is returned as-is with its current status — tools never block waiting for Bloom to finish, so the agent checks status and calls again rather than hanging.
The Content Intelligence scheduled template now recognizes Bloom as an alternative content-inventory signal, alongside Contentful.
Works from any MCP client on app.cogny.com/mcp.
Included in Cogny Solo ($9/mo).

What you can do with it

Area	What Claude can do
Account	Confirm the connection and see the workspace and credit balance behind the API key
Brands	Page through brands with name and status (`analyzing`, `ready`, `logo_required`, `failed`); read one brand's full detail
Brand Skill	Read a ready brand's generated profile — colors, typography, logo catalog — plus its Markdown summary files
Images	Page through generated images, optionally filtered to one brand; read one image's detail

In plain terms: "What brands do we have in Bloom, and which ones are ready?" "What's the color palette and typography for our main brand?" "How many images have we generated against it?" The answers come straight from the Bloom API without opening the app.

How to connect it

In Bloom, open Settings → API Keys and create a new key — name it e.g. Cogny.
Copy the generated key. It's shown once.
In your warehouse Settings → Cogny Managed MCPs, click Connect on the Bloom card and paste the key.

One API key per workspace. It's stored encrypted, sent only as the x-api-key header to trybloom.ai, and scoped to your single Cogny workspace.

On trust

This integration is read-only by construction, not just by convention — all six tools are GETs, and none of them pass wait=true to Bloom's long-running analysis or generation endpoints, so a brand or image that's still processing is returned with its current status rather than this server blocking on it. Logos and generated images are referenced by their signed, time-limited URL only — the proxy never downloads them or follows the link itself. There is no code path through which an agent could create a brand, edit one, generate an image or delete anything through Cogny.

Works with the Content Intelligence template

The Content Intelligence scheduled template now recognizes Bloom as an alternative content-inventory signal, alongside Contentful — if your brand and creative assets live in Bloom rather than (or alongside) a CMS, the template can fold that inventory into its recurring content-gap analysis.

Enable it from your warehouse Scheduled → + New scheduled prompt → Content Intelligence.

If your brand profile and generated creative live in Bloom, this is the connector that puts it on the same footing as every other source in your Cogny workspace. Connect it from your Cogny dashboard and ask your first question.