Repository avatar
Other Tools
v0.1.0
active

cliff-mcp

io.github.cliff-hq/cliff-mcp

Hardware parts with STEP files saved to disk for SolidWorks or any CAD tool, shop quotes and orders.

Documentation

Cliff MCP server

Hardware parts, CAD files, machining quotes and orders as MCP tools, for any MCP client: Claude Desktop, Claude Code, Cursor, or your own agent. Run it next to your CAD tool's MCP server (SolidWorks, Fusion, FreeCAD, Onshape) and your agent can:

  • find a bought part (screws, bearings, servos, connectors, boards) and save its STEP file to disk, ready to open or insert into an assembly;
  • upload a model you exported from your CAD tool by its path, and get Cliff's measures and machining plan for it;
  • split an assembly into its parts, name the stock ones, and save each made part as its own STEP file;
  • quote made parts at real shops at their own rates, keep a whole design as one priced BOM, and turn it into one checkout page that a person reviews and pays. Nothing is bought until they do.

Every tool is one call to Cliff's API (https://api.cliff.ai/v1). The server keeps no state of its own.

Set up

Node 20 or newer.

{
  "mcpServers": {
    "cliff": {
      "command": "npx",
      "args": ["-y", "@cliff-hq/mcp"],
      "env": { "CLIFF_API_KEY": "sk_..." }
    }
  }
}

Claude Code: claude mcp add cliff --env CLIFF_API_KEY=sk_... -- npx -y @cliff-hq/mcp

Searching parts, reading them, their CAD and their offers need no key. Uploading files, quotes, BOMs and checkouts need an API key from your Cliff account.

VariableMeaning
CLIFF_API_KEYyour account's key, sk_...
CLIFF_MCP_DOWNLOADSwhere files are saved (default ~/Downloads/Cliff)
CLIFF_API_URLthe API (default https://api.cliff.ai)

With SolidWorks

Add this server and a SolidWorks MCP server to the same client. A session might go:

  1. "Find an M3x12 socket head screw and put four in the motor mount": search_parts, then get_cad, which saves the STEP file and returns its path; the SolidWorks tools insert that file as a component.
  2. "What would this bracket cost to machine?": the SolidWorks tools export the part as STEP; upload_file sends that path; analyze_file and quote_made_part return Cliff's plan and each shop's price.
  3. "Price the whole assembly": export the assembly as STEP, upload_file, decompose_file (stock parts named, made parts as their own files), price_bom, then start_checkout for a page you approve.

Tools

ToolWhat it does
search_partsbought parts by name, part number, standard designation or what they must do
get_parta part's specs, stated tolerances, documents, attribution
get_cadthe part's STEP file (millimetres), saved to disk; path in the answer
get_offerssellers and prices for a quantity, each offer with a stable id
make_cartchosen offers as one cart a store, with each store's own cart link
upload_filea model or PDF print from a path on this computer
download_fileone of your files (a split assembly's part, a converted model) saved to disk
analyze_fileCliff's measures and machining plan for a process and material
convert_filea model as STEP, STL, OBJ or 3MF, saved to disk
decompose_filean assembly split into its distinct parts
list_shopsshops by process and material
quote_made_partone part, every shop's price at its own rates
quote_shop_orderseveral parts at one shop, as one order
price_bom, update_bom, get_boma design kept as one priced list; nothing is chosen for you
start_checkout, checkout_statusone page where a person reviews, approves and pays
request_removala rights holder's takedown request

Geometry measured from a STEP file is nominal, never a tolerance. Tolerances are given only where a vendor or a standard states them. Vendor files carry their attribution and a link back to the vendor.

Files and privacy

The server reads a file from your computer only when upload_file is called with its path, and only models, PDF prints and images (STEP, IGES, STL, OBJ, 3MF, native CAD formats, PDF, PNG, JPEG), up to 256 MB. It writes only into the downloads folder (or the save_to folder a tool call names), never over an existing file.

License

Apache License 2.0 (LICENSE, NOTICE). The license covers this server's code. Using Cliff's API, and the parts data, CAD files, quotes and orders it serves, is governed by Cliff's terms; vendor CAD files carry their own attribution and licence, returned with each file.

Contract

The tools are the same ones Cliff's hosted MCP server serves at https://api.cliff.ai/mcp, read from the same manifest (contract/mcp-tools.json), and every call is described in contract/openapi.json. The package's tests hold it to both, offline and against a running API (npm test; the live part runs when CLIFF_TEST_API_URL, CLIFF_TEST_API_KEY and CLIFF_TEST_STEP are set).

This repository is published from Cliff's monorepo, where the server and the contract are developed together; issues and pull requests are welcome here.

NPM
@cliff-hq/mcp
Install Command
npm install @cliff-hq/mcp