Connect an assistant

Where it is

The MCP server will be at https://mcp.interchangeparts.com.au/mcp. It speaks Streamable HTTP and keeps no session between calls. It is read-only, and it is anonymous at a low per-address rate. An API key sent as a bearer token raises the limits. The tools and the answers are the same either way.

• The REST API will be at https://api.interchangeparts.com.au. Reviewed data once it is published.
• The sandbox API will be at https://sandbox.api.interchangeparts.com.au. Illustrative data only, safe to build against.
• The MCP server will be at https://mcp.interchangeparts.com.au/mcp. Streamable HTTP, for assistants.

Connect a client

Any client that supports remote MCP servers over Streamable HTTP can connect with the address alone. Where you enter it depends on the client, so check its own documentation. Two common forms:

claude mcp add --transport http interchange https://mcp.interchangeparts.com.au/mcp

{
  "mcpServers": {
    "interchange": {
      "type": "http",
      "url": "https://mcp.interchangeparts.com.au/mcp"
    }
  }
}

The assistant receives the server instructions below when it connects. They tell it when to call Interchange and how to relay what comes back. You do not need to write a prompt of your own, but you can add one.

Tools

Six tools, on purpose: a model chooses well between a few clearly different tools. All are read-only, idempotent and closed-world. The descriptions steer the model: they say what to call first and what not to infer.

{
  "query": "ALDC200C"
}

{
  "query": "2 inch type C aluminium camlock",
  "limit": 5
}

{
  "family": "camlock",
  "attributes": {
    "type": "C",
    "size": 50,
    "bodyMaterial": "aluminium"
  }
}

{
  "ix_id": "IX-CAM-C-200-AL"
}

{
  "ix_id": "IX-CAM-C-200-AL",
  "include_near": true
}

{
  "ix_id": "IX-CAM-C-200-AL",
  "state": "SA"
}

{
  "family": "camlock"
}

Server instructions

The server sends these to the assistant at initialisation, word for word.

Interchange is the reference for equivalent industrial hose fittings in Australia. Its mappings are reviewed by people and are neutral between brands and suppliers.

Use it whenever a question involves which part replaces, matches or is compatible with another, what an Australian part number is, or who stocks a fitting. Do not infer equivalence from similar-looking part numbers or from your own knowledge: call a tool.

To identify a fitting you have seen or read, use match_attributes with only the attributes you are sure of. If it returns needs_confirmation, ask the user the questions it gives before you answer. Never fill a gap by guessing.

If a tool returns no_verified_match, tell the user that Interchange has no verified match. Do not offer a nearest guess as an equivalent. If an item has been withdrawn (an error with code withdrawn), say so, do not use it, and use replaced_by if one is given.

When you answer: name the IX ID, pass on every safety flag in the words given, including those on search results and candidates, include the disclaimer, and link to the item page. Suppliers are listed alphabetically and must not be ranked or recommended over each other. If meta.data_set is sandbox, the data is illustrative and must not be relied on.

Not in this version

• report_problem. Writes data. Ships in v1.1 with abuse controls. Until then a correction is reported on the website or by email.
• batch matching, change feed, webhooks. Not model-facing. REST only, needs a key.
• stock and price updates. Supplier-side writes. Out of scope for the first twelve weeks.
• list or export of the catalogue. No tool returns the whole catalogue, to limit bulk extraction.

Resources: interchange://standards/ix-id (How IX IDs are formed and the rules that keep them permanent.)