Brick Directory

directory.brickPublished by brick.directoryOfficial publisherv2025.11.17.0708Updated Oct 24, 2026

Provides data for LEGO sets, minifigures, parts and elements. Not affiliated with LEGO® Group.

VerifiedStreamable HTTPWeb executable

Overview

AI-generated overview

A remote MCP server that gives an assistant LEGO set, minifigure, part and element data from Brick Directory, with OAuth sign-in required.

What you can do
Look up LEGO sets, minifigures, parts and elements through the Brick Directory service. The manifest lists no individual tools, so the exact operations are not documented here. Access is through a hosted remote endpoint rather than a local package.
When to use it
Useful when an assistant needs reference data about LEGO sets, minifigures, parts or elements, for example to answer questions about a set or its contents. Not needed if your work does not involve LEGO catalog data.
Requirements
A remote MCP connection to the Brick Directory endpoint over streamable HTTP. OAuth authentication is required, so you need a Brick Directory account or an OAuth flow the service accepts. No environment variables or headers are declared.
Before you install
Sign-in is required, so the service receives your account identity and any queries you make. The manifest lists no tools, so what the assistant can read or change is not documented; check the provider's terms before connecting. The service states it is not affiliated with the LEGO Group.

Installation

In SourceWeft

  1. Open Brick Directory 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/directory.brick%2Fmcp/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": {
    "brick-directory": {
      "type": "http",
      "url": "https://api.brick.directory/connect"
    }
  }
}

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. v2025.11.17.0708LatestSep 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.