MCP server

The TracePass MCP server lets an AI assistant drive the TracePass platform directly — list and create products, build and audit Digital Product Passports, set economic-operator parties, and read or capture GS1 EPCIS supply-chain events. It speaks the full Model Context Protocol: tools, resources, and prompts. Connect a hosted endpoint or run it locally via npx — both authenticate with the same tp_ API keys as the v1 API. Source on GitHub, published as tracepass-mcp-server on npm.

What it is

MCP is an open protocol that lets an AI assistant call external tools and read external data through a single, standard interface. The TracePass MCP server is a thin, stateless adapter in front of the TracePass v1 API — it has no database of its own; every tool call and resource read goes straight through to the same API your other integrations use, so authentication, plan gating, and rate limits all behave identically. There are two ways to connect it. The hosted server runs at https://ai.tracepass.eu/mcp over HTTP — nothing to install, always current. The local server is the tracepass-mcp-server npm package, launched as a subprocess by your MCP client and speaking MCP over stdio.

Connecting (hosted)

Point your MCP client at the hosted endpoint and pass your API key as a Bearer token. Mint a key in the dashboard under Developer → API Keys — it is the same tp_key the v1 API uses. Add this block to your client's MCP configuration:

json

{
  "mcpServers": {
    "tracepass": {
      "url": "https://ai.tracepass.eu/mcp",
      "headers": { "Authorization": "Bearer tp_YOUR_KEY" }
    }
  }
}

Connecting (local / npx)

For a local setup, your MCP client launches the npm package as a subprocess and talks to it over stdio. There is nothing to install ahead of time — npx fetches tracepass-mcp-server on first run. The API key is passed through the TRACEPASS_API_KEY environment variable instead of a header:

json

{
  "mcpServers": {
    "tracepass": {
      "command": "npx",
      "args": ["-y", "tracepass-mcp-server"],
      "env": {
        "TRACEPASS_API_KEY": "tp_YOUR_KEY"
      }
    }
  }
}

Tools

The TracePass v1 API operations are grouped into five tools. Each takes an action plus action-specific args, so the assistant picks the tool by domain and the operation by action:

Tool	Actions
`tracepass_products`	`list, get, create, update` Catalog operations — browse, read, and create or update products.
`tracepass_passports`	`list, get, get_by_serial, create, suspend, archive, get_qr` The passport lifecycle — list and read passports, look one up by serial number, create, suspend, archive, and fetch the QR code.
`tracepass_passport_fields`	`update` Update individual template fields on a passport.
`tracepass_passport_parties`	`set, remove` Set or remove economic-operator parties (manufacturer, importer, recycler, and so on) on a passport.
`tracepass_epcis`	`export, capture, capture_job, query` Read and write GS1 EPCIS 2.0 supply-chain events — export a passport's event history, capture new events, run a capture job, and query the event store.

Some write actions cost money or are irreversible.The server's tool descriptions tell the model this, but you should know it too: tracepass_passports with action create consumes a billable DPP slot on your plan — over-quota creation incurs a per-passport overage charge and only proceeds once the user agrees via confirmOverage. Action archive is irreversible; use suspend when you may need the passport back. The tracepass_epcis actions (capture, query, export) are included on every paid plan and metered by events-per-month per the plan table on /pricing.

Resources

Resources are read-only entity data the user attaches as conversation context, addressed by a tracepass:// URI. One is a static resource, the rest are resource templates the client completes with an id:

tracepass://products
tracepass://product/{id}
tracepass://passport/{id}
tracepass://passport/{id}/epcis

Prompts

Prompts are reusable DPP workflows the MCP client surfaces to the user, typically as slash-commands. Each seeds the conversation so the assistant carries out the task the way TracePass intends — for example, always confirming before it creates a billable passport:

audit_passport
onboard_product
review_epcis_events