Brixa Studio

com.brixastudioPublished by brixastudio.comOfficial publisherv1.0.2Updated Oct 24, 2026

Your design, automated endlessly. Design anywhere, Brixa freezes it as a template, publishes forever

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Brixa Studio is a remote MCP endpoint that lets an assistant turn a design into a reusable template and publish it repeatedly.

What you can do
The registry description is brief: it presents the service as automating design endlessly, and as letting you design anywhere, freeze the result as a template, and publish it forever. No tools are listed in the manifest, so the specific actions an assistant can take are not documented here.
When to use it
Consider it when you want an assistant to help capture a finished design as a reusable template and republish it, rather than doing one-off design work. Because the tool list is not published, confirm the available actions before relying on it.
Requirements
A remote streamable HTTP endpoint at the provider's hosted address; no local package or runtime is needed. Authentication is OAuth and is required, so you need an account with the provider and a client that supports the OAuth flow. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to a third-party hosted service, so review the scopes requested at sign-in. The description mentions publishing, which may make content publicly visible; check what gets published and who can see it. Tool behavior is not documented in the manifest.

Installation

In SourceWeft

  1. Open Brixa Studio 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.brixastudio%2Fstudio/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": {
    "brixa-studio": {
      "type": "http",
      "url": "https://mcp.brixastudio.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.2LatestSep 16, 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.