rainbrand.com
Rainbrand is a service for turning a brand’s identity, guidance, and assets into maintained, versioned context that agents and applications can use. It supports brand onboarding, task-specific briefs, generation workflows, review, and asset/library management.
Rainbrand exposes two developer integration surfaces on its own domains: a REST API at https://www.rainbrand.com/api/v1 authenticated by API key or OAuth bearer token, and an OAuth-protected remote MCP server at https://mcp.rainbrand.com/mcp that self-onboards via DCR and also declares API-key header support.
- Rainbrand MCPdetected
- Rainbrand APIdiscovered
- Rainbrand APIdeclared
In Rainbrand account settings, generate an API key and store it as RAINBRAND_API_KEY in your environment or secret manager. Keep it server-side; docs say keys start with bloom_sk_. You can send the same key either in the x-api-key header or as Authorization: Bearer <key>. If both are present, x-api-key takes precedence. See Authentication.
Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.
conventions · 4/8 published
- integrations.json✓https://rainbrand.com/.well-known/integrations.json
- llms.txt✓https://rainbrand.com/llms.txt
- API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✓https://mcp.rainbrand.com/mcp
- OAuth protected resource✓https://rainbrand.com/.well-known/oauth-protected-resource
- Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing