Image Generator
shinprLABSCO SUMMARY
Moderation being a parameter rather than a default is the thing to configure before an agent starts generating.
When a human drives image generation, an unmoderated prompt is their own problem. When a model does, the prompts are generated too — and the safety parameters have to be set in the integration rather than remembered per call. Bria documents them clearly; set them once. The licensing position is the other reason this appears in commercial stacks where a general-purpose generator would not.
What it is
Bria's production endpoint for their visual generation API — the company's position is that its models are trained on licensed data, which is the reason enterprises pick it.
What you get
Bria's image generation and editing surface.
Requirements
A static API key in the api_token header, or a long-lived OAuth 2.0 bearer token. Moderation is opt-in through API parameters such as prompt_content_moderation rather than being on by default.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Generating imagery you can use commercially
Bria's licensed-data position is the reason to reach for this rather than a general generator.
02
Keeping generated prompts in bounds
Set the moderation parameters in the integration so every agent-written prompt is checked.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- Static API key (api_token header) or OAuth 2.0 long-lived Bearer token (authorization_token)
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://mcp.prod.bria-api.com/mcpRequirements
- Static API key (api_token header) or OAuth 2.0 long-lived Bearer token (authorization_token)
