Back to homeFor AI agents

MCP Server

BuildBox runs a Model Context Protocol (MCP) server, so an AI assistant you trust — Claude or any MCP-capable client — can browse the parts catalog, check compatibility, and assemble a complete PC for a budget, directly. It proposes builds; you review and order. It never orders or takes payment.

Endpoint

Point your MCP client at this HTTP endpoint:

POST https://buildboxapp.com/api/mcp

Transport: Streamable HTTP, JSON-RPC 2.0 — POST one message or a batch; no SSE. It implements initialize, tools/list, tools/call and ping.

Read tools are anonymous — no account or API key needed. Saving a build attributes it to a shared guest account and returns a link you open on the site.

How to connect

Add BuildBox as a remote MCP server in your client's config. The exact format varies by client; a typical entry looks like:

{
  "mcpServers": {
    "buildbox": {
      "type": "http",
      "url": "https://buildboxapp.com/api/mcp"
    }
  }
}

Some clients add a remote server from the UI instead of a file — just paste the endpoint URL above. BuildBox uses Streamable HTTP (not SSE).

  1. 1Add the endpoint above to your MCP client (config file or an “add server” dialog).
  2. 2The client calls tools/list and discovers BuildBox's seven tools.
  3. 3Ask in plain language — e.g. “assemble a $1500 gaming PC for 1440p” — and the assistant uses the tools, then hands you a build to review.

What the assistant can do

Seven tools, each wrapping the same logic the site itself uses. Parts are referenced by a public slug.

list_categoriesList the component categories BuildBox builds with.
search_partsFree-text search across the catalog (brand, model, or keyword).
list_partsList parts in a category, optionally capped by price or brand.
get_partFull detail for one part — price, description, and the full spec table.
check_compatibilityCheck a set of parts for socket, memory, power, and clearance issues.
assemble_buildTurn a budget + use case into 2–3 complete, compatible build options (in-budget, ≈10% and ≈20% over) with a rationale for each.
create_buildSave a chosen parts list and get a shareable build link to review on the site.

Try it from the terminal

Every tool is a plain JSON-RPC call. List the available tools with curl:

curl -X POST https://buildboxapp.com/api/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

What it will never do

The MCP server stops before any transaction. No tool orders, pays, enters an address, or touches an account. The assistant assembles and saves a build; a person opens the link, reviews it, and buys on BuildBox. Financial actions stay with you.

FAQ

What is the BuildBox MCP server?
An HTTP endpoint that lets an MCP-capable AI assistant work with BuildBox directly — browse the catalog, check part compatibility, and assemble a build for a budget — without copying data around by hand.
How do I connect my assistant?
Add the endpoint (buildboxapp.com/api/mcp) as a remote MCP server in your client. Read tools need no account; the assistant then discovers the tools and uses them when you ask.
Can the assistant place an order or pay?
No. The tools never order, pay, set an address, or change account settings. The assistant can only assemble and save a build and return a link — you review and buy on the site yourself.
Do I need an API key or login?
No. Browsing and assembling are anonymous. Saving a build uses a shared guest account and returns a public link you can open and fork into your own account before ordering.
Open the builderBrowse the catalog