Ordering opens soon. Until then, write to support@uliketechnology.com and an engineer answers.

All guides

AI assistants

What MCP is and how agents order

The Model Context Protocol in plain terms, why a factory offers tools to AI agents, our safety model, and the tools an assistant can use here.

Updated 2026-11-177 min read

What MCP is

The Model Context Protocol (MCP) is an open standard that lets an AI assistant use outside services in a uniform way. A service publishes a list of tools. Each tool has a name, a description, the inputs it takes and the shape of what it returns. The assistant reads the list, picks a tool when the conversation calls for it, and gets a structured answer back.

The drawing shows the shape of our MCP server.

An assistant on the left, a list of tools in the middle with read tools on top, write tools below and one amber tool at the bottom, and the site on the right
  1. The assistant reads the list of tools and picks one when the conversation calls for it.
  2. Read-only tools: capabilities, the design, the check report, quotes, orders and messages.
  3. Tools that write: uploads, quotes and messages.
  4. The tool that leads to an order can only prepare one. You approve it on the site.
  5. The site answers in a structured shape, with exact numbers.

For you the effect is simple. Instead of the assistant guessing how a website works, the website tells the assistant exactly what it can do. The assistant can then do things like "check this board file" or "show me a price" in a way that is exact and repeatable.

Why a factory offers tools instead of a web form

A web form is made for human eyes. An assistant using one has to look at screenshots or scrape the page, and it breaks when the page changes.

A tool list is made for software. It says what each step needs and what comes back. For a circuit board order that matters, because the steps are precise: upload files, read the check report, change an option, read the price, confirm. Each step has numbers that must be exact, for example a hole size in micrometres or a price in a currency. Structured answers keep them exact.

Tools also make safety easier. A tool can say plainly that it spends money, and an assistant can be built to ask you before it uses such a tool. A web form gives no such signal.

What exists today

The MCP server. Its address is https://uliketechnology.com/api/mcp. Without sign-in an assistant can read what we make, open a guest session, send a board to the file check and get prices, within a daily allowance. To let an assistant work with your account, connect https://uliketechnology.com/api/mcp/account: it asks the assistant to sign in as you. The assistant can then also read your orders, prepare an order for you to approve, and read and write your messages with the factory.

Two ways to connect. An assistant signs in as you: it opens a page of this site in your browser that shows its name, its address and what it asks to do, and nothing is allowed until you press Allow. Or you make an API key in your account, choose what it may do, and give the key to your own program. Both act as you, within the permissions you chose, and you can end the access at any time. For developers and assistants has the addresses and the steps.

The REST API. It is the same service without MCP: upload, file check, quote and order. The API quickstart shows the calls.

The safety model

It rests on four rules.

  1. An agent always works for a signed-in person. Agents have no accounts of their own. You sign in with your own account, and you allow the agent to act for you with named permissions. You can take the permission back.
  2. The agent can prepare an order. It cannot place it, and it cannot pay. When an assistant that signed in for you asks to place an order, the answer is "approval required" and a link to our site. Nothing is ordered yet. You open the link, sign in, see the exact order and total, and approve or decline. The link works once, is bound to your account, runs out after 24 hours, and stops working if the quote or the total changes. Payment is by bank transfer, which you make yourself.
  3. An engineer confirms every order. Whoever placed it, an engineer checks the files and the order before production starts.
  4. Every tool says what kind it is. A tool is marked as read-only, as one that writes a record, or as one that commits. The two that commit, placing and cancelling an order, take a key that makes a repeated call happen once.
Four boxes in a row: you, the assistant, the site and an engineer, with arrows between them and an amber path from the site back to you
  1. You sign in with your own account and allow the agent to act for you.
  2. The agent prepares an order. It cannot place it or pay.
  3. The site shows the exact order and total behind a link.
  4. An engineer confirms every order before production.
  5. The amber path is the approval link. The agent passes it to you, and it works only for you, signed in.

There is deliberately no tool that pays, that adds or changes an address, or that makes an API key. Those are done only in the browser, where you are.

An API key works the same way. It is your own program acting as you, and an order it sends is prepared, not placed: the answer is the approval link, and the order is placed after you approve it on the site.

We also treat text from your files as data. File names, text inside design files and BOM descriptions come back in fields of limited length, never as instructions. Each tool's description names the fields that carry such text and tells the assistant not to follow anything written there. Text in a file cannot change what the agent is allowed to do.

The tools

These are the tools the server offers. An assistant sees only the ones it may use: without sign-in the first five groups, and after you connect your account the ones your permissions cover.

Group Tools
Read what we can make get_capabilities
Work without an account start_guest_session
Upload and read a board create_upload_session, complete_upload, list_designs, get_design, set_layer_mapping
Check validate_design, get_validation_report
Quote preview_quote, create_pcb_quote, list_quotes, get_quote, update_quote_options
Addresses list_addresses
Order place_order, list_orders, get_order, cancel_order, answer_engineering_query
Messages with the factory list_threads, get_thread, create_thread, post_thread_message, mark_thread_read, close_thread

place_order answers the approval link described above. cancel_order works only before an order is released to production. A question that the factory marked as personal cannot be answered through an assistant: the tool refuses and tells the assistant to show you the question.

The server also carries our design guide for assistants as a resource, ulike://guide/pcb-design, and a prompt, check-and-quote-a-board, that walks an assistant through upload, check and quote.

What an order through an assistant looks like

Say you ask an assistant to order twenty boards. It reads the capabilities, sends your zip to the upload address, reads the check report and tells you what it found. It creates a quote and shows you the price. Where a price needs an engineer, the quote can be ordered after the engineer has confirmed it. The assistant then prepares the order and gives you a link. You open it, sign in, check the total and the address, and approve. The order page shows the bank details and the reference for your transfer. An engineer confirms the order, and production starts when your payment has arrived.

At no point does the assistant hold payment details. At no point can an assistant that signed in for you place an order without your approval. If its answer looks wrong, you see it on the approval page before anything is ordered.

What MCP does not change

MCP is a way to reach the same service. It adds no new powers. An agent using the MCP server meets the same file check, the same limits, the same prices and the same engineer review as a person using the website. The permissions you give an agent are never wider than your own. A tool can only do what its permission allows, and you can remove the permission at any time.

What you can do now

Add the address of the MCP server to an assistant that supports MCP, or make an API key for your own program. For developers and assistants shows both. If you work with an assistant, give it our PCB design guide for AI assistants. If you want to know how to work with an assistant in general, read Ordering boards with an AI assistant.