Lego MCP Server

LEGO sets, parts, minifigs, and inventories as an MCP server

Local serverstdio

What is the Lego MCP server?

Most developer tooling work still happens through a UI a human drives. Lego MCP server moves it into the conversation instead. LEGO sets, parts, minifigs, and inventories as an MCP server.

Getting it running

lego-oracle on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

The tools it exposes

The server publishes 10 tools. What each one is for:

  • search_sets — Search for sets by name, theme, year, or piece count. Full-text search with filters
  • get_set — Get complete set details: inventory (grouped by part category), minifigures, theme hierarchy
  • compare_sets — Compare 2-4 sets side by side: piece count, year, theme, minifigs, shared parts
  • search_parts — Search parts by name, category, colour, or material
  • get_part — Get part details including available colours and mold/print variants
  • find_part_in_sets — Find which sets contain a specific part (optionally in a specific colour), sorted by quantity
  • search_minifigs — Search minifigures by name
  • get_minifig — Get minifig details and every set it appears in
  • browse_themes — Browse the LEGO theme hierarchy. Top-level themes or drill into sub-themes with set counts
  • find_mocs — Find community alternate builds (MOCs) for a set's parts

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Lego.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Lego's toolset — search_sets, get_set, compare_sets and 7 more — is a fair guide to whether it matches your workflow. It is maintained by gregario; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
search_setsSearch for sets by name, theme, year, or piece count. Full-text search with filters.
get_setGet complete set details: inventory (grouped by part category), minifigures, theme hierarchy.
compare_setsCompare 2-4 sets side by side: piece count, year, theme, minifigs, shared parts.
search_partsSearch parts by name, category, colour, or material.
get_partGet part details including available colours and mold/print variants.
find_part_in_setsFind which sets contain a specific part (optionally in a specific colour), sorted by quantity.
search_minifigsSearch minifigures by name.
get_minifigGet minifig details and every set it appears in.
browse_themesBrowse the LEGO theme hierarchy. Top-level themes or drill into sub-themes with set counts.
find_mocsFind community alternate builds (MOCs) for a set's parts.

How to install the Lego MCP server

{
  "mcpServers": {
    "lego-oracle": {
      "command": "npx",
      "args": ["-y", "lego-oracle"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Lego to search sets.
  • Use Lego to get set.
  • Use Lego to compare sets.

Frequently asked questions

It connects Lego to MCP-compatible AI assistants such as Claude and Cursor, exposing 10 tools (search_sets, get_set, compare_sets, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Lego directly.