Bria

com.bria-apiPublished by bria-api.comOfficial publisherv1.0.0Updated Oct 24, 2026

Commercially licensed image generation and editing with IP indemnification.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Bria provides commercially licensed image generation and editing with IP indemnification through a remote MCP endpoint.

What you can do
Bria is a remote MCP server for commercially licensed image generation and editing, offered with IP indemnification. The manifest lists no individual tools, so the exact operations are not documented here. Access is authenticated with a Bria API token.
When to use it
Consider it when an assistant needs to create or edit images for commercial use and the licensing and IP indemnification terms matter.
Requirements
A remote streamable HTTP endpoint at mcp.prod.bria-api.com. Authentication is OAuth and required, with an api_token header carrying a Bria API token. No packages or environment variables are declared.
Before you install
A Bria API token is a secret sent in the api_token header; keep it private. Image generation may consume paid Bria credits or quota, and generated or edited images are sent to Bria's service. Licensing and indemnification terms should be reviewed before commercial use.

Installation

In SourceWeft

  1. Open Bria in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.bria-api%2Fbria-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "bria": {
      "type": "http",
      "url": "https://mcp.prod.bria-api.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 15, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.