tracepass-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRACEPASS_API_KEY | Yes | Your TracePass API key (starts with tp_) | |
| TRACEPASS_BASE_URL | No | Base URL for TracePass API (default: https://app.tracepass.eu) | https://app.tracepass.eu |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tracepass_productsA | Manage the TracePass product catalogue. A product is the catalogue layer — one product can have many passports (one per serialised unit). Products are not billable on their own. Actions (pass via
|
| tracepass_passportsA | Manage Digital Product Passports — create, read, and run lifecycle actions. IMPORTANT: Actions (pass via
|
| tracepass_passport_fieldsA | Update field values on a Digital Product Passport. Every change is recorded in the passport's audit trail, tagged as an API-key update. Actions (pass via
|
| tracepass_passport_partiesA | Manage the economic-operator parties on a passport — manufacturer, importer, authorisedRepresentative, distributor, recycler, producerResponsibilityOrg. Each party carries a legal name and ideally a validated 13-digit GS1 GLN. Actions (pass via
|
| tracepass_epcisA | GS1 EPCIS 2.0 supply-chain events. Actions (pass via
|
| tracepass_templatesA | Discover the regulatory field schema for each DPP category — what a COMPLIANT passport must contain, per the governing EU regulation. Read-only reference data. Use this to advise on requirements before creating products/passports, and to gap-check a draft against the rules. Actions (pass via
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| audit_passport | Review one Digital Product Passport for completeness and compliance readiness — which required fields are missing, which economic-operator parties are unset, whether it's publishable. |
| onboard_product | Walk through creating a new product and its first Digital Product Passport — gathering the details, then creating both. |
| explain_dpp_requirements | Explain what a Digital Product Passport in a given category must contain to be compliant — the required fields and the EU regulation behind them — before you create anything. |
| compliance_gap_check | Cross-check a draft passport against its category's regulatory schema and produce an exact, prioritised list of what's missing before it can be published compliantly. |
| review_epcis_events | Inspect the EPCIS 2.0 supply-chain event history of a passport and summarise the product's traceability story. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| products | The account's TracePass product catalogue (first page). Attach this for an overview of what products exist. |
| templates | All 12 DPP category schemas with field count, required-field count, and governing regulation. Attach this to ground the model in what each category's compliance requirements are. |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/malinoto/tracepass-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server