Tracepass MCP server
{
"mcpServers": {
"tracepass": {
"type": "http",
"url": "https://ai.tracepass.eu/mcp"
}
}
}{
"mcpServers": {
"tracepass": {
"type": "http",
"url": "https://ai.tracepass.eu/mcp"
}
}
}{
"mcpServers": {
"tracepass": {
"type": "http",
"url": "https://ai.tracepass.eu/mcp"
}
}
}{
"servers": {
"tracepass": {
"type": "http",
"url": "https://ai.tracepass.eu/mcp"
}
}
}{
"mcpServers": {
"tracepass": {
"type": "http",
"url": "https://ai.tracepass.eu/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y tracepass-mcp-serverversion 1.7.4
What it does
An MCP server for TracePass, the EU Digital Product Passport platform. It exposes tools to manage products, Digital Product Passports, economic-operator parties, and GS1 EPCIS supply-chain events. For developers building AI assistants or applications that need to read or write product passport data.
- Create and manage Digital Product Passports for products in your catalogue, including compliance and registry-readiness checks.
- Track and query GS1 EPCIS supply-chain events for products to maintain supply-chain visibility.
- Update product data and assign economic-operator parties (manufacturers, importers, etc.) to passports.
Tools this server exposes
| Tool | Does |
|---|---|
| tracepass_products | List, get, create, batch create, update, or archive products in the catalogue. |
| tracepass_passports | List, get, create, suspend, archive, or retrieve QR codes for Digital Product Passports; check compliance and registry readiness. |
| tracepass_passport_fields | Update category-specific data fields on a passport. |
| tracepass_passport_parties | Set or remove economic-operator parties (manufacturer, importer, etc.) on a passport. |
| tracepass_epcis | Export, capture, and query GS1 EPCIS 2.0 supply-chain events for a passport. |
| tracepass_templates | List and get DPP category field schemas, with traceability to EU regulatory requirements. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.