2nd Brick

io.github.noahgsolomonPublished by GitHub account noahgsolomonv1.0.0Updated Oct 26, 2026

Design custom LEGO brick sets with 3D models, instructions, kit prices and customer-paid checkout.

The publisher's own server: brick.blue

VerifiedStreamable HTTPWeb executableBusiness & CommerceMedia & Design

Overview

AI-generated overview

Remote MCP server for 2nd Brick that lets an assistant design custom LEGO brick sets with 3D models, instructions, kit prices and customer-paid checkout.

What you can do
  • Design custom LEGO brick sets, including 3D models and building instructions.
  • Price kits and set up customer-paid checkout for the designs.
  • No tool list is published, so the exact actions available are not documented; capabilities are inferred from the service description.
When to use it
Useful when you want an assistant to help create or price a custom LEGO brick set and move it toward a customer-paid order, rather than for general design or ecommerce work.
Requirements
A remote endpoint at 2ndbrick.com over streamable HTTP, with OAuth authentication. An Authorization header carrying a bearer key from a Studio Pro account is required; the key is obtained from the provider's account agents page.
Before you install
The server requires a bearer key in the Authorization header, so treat it as a secret. Designs can lead to customer-paid checkout, meaning real orders and money; confirm prices and orders before anything is submitted.

Installation

In SourceWeft

  1. Open 2nd Brick 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/io.github.noahgsolomon%2F2nd-brick/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": {
    "2nd-brick": {
      "type": "http",
      "url": "https://2ndbrick.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 17, 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.

Other Brick integrations