Tracelink MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRACELINK_TOKEN | Yes | Your API token for Tracelink |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_companyB | Henter Tracelink virksomhedens stamdata |
| list_departmentsA | Henter liste over afdelinger i virksomheden |
| get_current_userA | Henter den aktuelt autentificerede bruger |
| list_usersB | Henter liste over alle brugere i systemet |
| list_user_groupsB | Henter liste over brugergrupper |
| list_ordersA | Henter liste over ordrer. Brug ved spørgsmål om aktive ordrer, deadlines, status eller fremdrift. |
| get_orderA | Henter en specifik ordre med alle detaljer |
| create_orderC | Opretter en ny ordre i Tracelink |
| update_orderC | Opdaterer en eksisterende ordre |
| delete_orderB | Sletter en ordre permanent |
| list_subordersC | Henter liste over underordrer |
| get_suborderB | Henter en specifik underordre |
| create_suborderB | Opretter en underordre på en eksisterende ordre |
| list_objectsB | Henter objekter fra et Tracelink modul. Tilgængelige moduler: purchase, genobj, customer, supplier, crm, docs, batch_genobj, stockloc, ticket, bait |
| get_objectB | Henter et specifikt objekt fra et modul |
| create_objectC | Opretter et nyt objekt i et modul (f.eks. en indkøbsordre, kunde, leverandør) |
| update_objectB | Opdaterer et objekt i et modul |
| list_order_moduleC | Henter registreringer fra et ordre-modul, f.eks. tidsregistreringer eller opgaver |
| add_order_moduleC | Tilføjer en registrering til et ordre-modul, f.eks. tidsregistrering |
| list_journalA | Henter journal/chat beskeder for et specifikt objekt i et modul |
| add_journalB | Tilføjer en journal besked eller hændelse til et objekt i et modul |
| list_relationsC | Henter relationer mellem to moduler |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
Each tool targets a distinct entity and action (e.g., create_object vs. create_order, list_objects vs. list_orders). Descriptions clearly differentiate overlapping concepts like orders and suborders, leaving no ambiguity.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., add_journal, create_object, list_orders). No mixing of conventions or irregular naming.
With 22 tools covering objects, orders, suborders, users, departments, journals, and relations, the count is well-scoped for an enterprise system. Each tool serves a necessary purpose without redundancy.
Significant gaps exist: no delete_object, no update/delete for suborders, and many entities (companies, users, departments) only have list/get tools with no create/update/delete. This will cause agent failures in full lifecycle operations.