Skip to main content
Glama
Tracelink MCP Server

Tracelink MCP Server

Official

Tracelink MCP Server

MCP server that gives Claude, ChatGPT and GitHub Copilot access to the Tracelink API.

There are two ways to connect: a hosted HTTPS server (recommended) or the local stdio server in this repo.

  • HTTPS — Tracelink hosts the server at https://tracelink.dk/api/mcp. Your client talks to it directly over the internet, authenticating with an API key in the x-access-token header. No installation, no local process, always up to date, and it exposes a broader/better tool set (e.g. document upload, tags, relations, schema introspection).

  • stdio — the client starts this repo's index.js as a local child process and talks to it over stdin/stdout. Requires Node.js, a local checkout, and npm install.

The stdio server in this repo is no longer being actively developed and will be removed at a later point. New setups should use the hosted HTTPS server below; existing stdio configurations should migrate when convenient.

Connect directly to Tracelink's hosted MCP server at https://tracelink.dk/api/mcp. This requires no local installation — just an API key sent via the x-access-token header.

You can configure this either by editing the config file directly (examples below), or through the user interface:

  • Claude Desktop: Settings → Connectors → Add custom connector, enter the URL https://tracelink.dk/api/mcp and add a header named x-access-token with your API key.

  • VS Code: Run the command "MCP: Add Server" from the Command Palette, choose "HTTP", enter the URL https://tracelink.dk/api/mcp, and add a header named x-access-token with your API key.

Claude Desktop

{
  "mcpServers": {
    "tracelink": {
      "type": "http",
      "url": "https://tracelink.dk/api/mcp",
      "headers": {
        "x-access-token": "your-api-key-here"
      }
    }
  }
}

VS Code (GitHub Copilot)

{
  "servers": {
    "tracelink": {
      "type": "http",
      "url": "https://tracelink.dk/api/mcp",
      "headers": {
        "x-access-token": "your-api-key-here"
      }
    }
  }
}

ChatGPT

Custom MCP connectors require Developer mode, which must be enabled first:

  1. Go to Settings → Connectors → Advanced settings and turn on Developer mode.

  2. Go back to Settings → Connectors and click Create (or Add custom connector).

  3. Fill in a name (e.g. Tracelink), and set the MCP Server URL to https://tracelink.dk/api/mcp.

  4. Under Authentication, choose the API key / custom header option, set the header name to x-access-token, and enter your API key as the value.

  5. Save, then enable the Tracelink connector in a chat via the + → More → Connectors menu (or in Deep Research) to make its tools available.

Availability of custom connectors and the exact menu wording depends on your ChatGPT plan (Plus/Pro/Team/Enterprise) and may change over time.

Related MCP server: claude-for-abap

Local stdio server (deprecated)

⚠️ This local server is no longer actively developed and will be removed at a later point. Use the hosted HTTPS server above instead.

Installation

npm install

Configuration in Claude Desktop

Add the following to your Claude Desktop config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "tracelink": {
      "command": "node",
      "args": ["/full/path/to/tracelink-mcp/index.js"],
      "env": {
        "TRACELINK_TOKEN": "your-api-token-here"
      }
    }
  }
}

Restart Claude Desktop — the server starts automatically.

Configuration in VS Code (GitHub Copilot)

Requires VS Code 1.99+ and GitHub Copilot with Agent mode enabled.

Create .vscode/mcp.json in your workspace:

{
  "servers": {
    "tracelink": {
      "type": "stdio",
      "command": "node",
      "args": ["/full/path/to/tracelink-mcp/index.js"],
      "env": {
        "TRACELINK_TOKEN": "your-api-token-here"
      }
    }
  }
}

Tools are then available in Copilot Chat when Agent mode is active.

Available tools (stdio server)

The hosted HTTPS server exposes a broader tool set (including document upload, tags, relations, and schema introspection); the table below lists only what the local stdio server supports.

Tool

Description

get_company

Company master data

list_departments

Departments

get_current_user

Current authenticated user

list_users

All users

list_user_groups

User groups

list_orders

Orders with filter/sort/paging

get_order

Specific order

create_order

Create order

update_order

Update order

delete_order

Delete order

list_suborders

Suborders

get_suborder

Specific suborder

create_suborder

Create suborder

list_objects

Objects from a module (purchase, genobj, customer, ...)

get_object

Specific object

create_object

Create object

update_object

Update object

list_order_module

Time registrations / tasks on an order

add_order_module

Add time registration / task

list_journal

Journal/chat messages on an object

add_journal

Add message or event to journal

list_relations

Relations between modules

Available Tools

22 tools
add_journalB

Tilføjer en journal besked eller hændelse til et objekt i et modul

Inputs: module (required), item_id (required), type (required), log (required), +2 more.

add_order_moduleC

Tilføjer en registrering til et ordre-modul, f.eks. tidsregistrering

Inputs: module (required), data (required).

create_objectC

Opretter et nyt objekt i et modul (f.eks. en indkøbsordre, kunde, leverandør)

Inputs: module (required), data (required).

create_orderC

Opretter en ny ordre i Tracelink

Inputs: name (required), number, description, deadline_date, +5 more.

create_suborderB

Opretter en underordre på en eksisterende ordre

Inputs: order_id (required), name (required), number, description.

delete_orderB

Sletter en ordre permanent

Inputs: order_id (required).

get_companyB

Henter Tracelink virksomhedens stamdata

Inputs: no named parameters.

get_current_userA

Henter den aktuelt autentificerede bruger

Inputs: no named parameters.

get_objectB

Henter et specifikt objekt fra et modul

Inputs: module (required), object_id (required).

get_orderA

Henter en specifik ordre med alle detaljer

Inputs: order_id (required).

get_suborderB

Henter en specifik underordre

Inputs: order_sub_id (required).

list_departmentsA

Henter liste over afdelinger i virksomheden

Inputs: no named parameters.

list_journalA

Henter journal/chat beskeder for et specifikt objekt i et modul

Inputs: module (required), item_id (required).

list_objectsB

Henter objekter fra et Tracelink modul. Tilgængelige moduler: purchase, genobj, customer, supplier, crm, docs, batch_genobj, stockloc, ticket, bait

Inputs: module (required), filter, filter_or, sort, +3 more.

list_order_moduleC

Henter registreringer fra et ordre-modul, f.eks. tidsregistreringer eller opgaver

Inputs: module (required), order_id.

list_ordersA

Henter liste over ordrer. Brug ved spørgsmål om aktive ordrer, deadlines, status eller fremdrift.

Inputs: filter, filter_or, sort, reverse, +2 more.

list_relationsC

Henter relationer mellem to moduler

Inputs: from_module (required), to_module (required), to_id (required).

list_subordersC

Henter liste over underordrer

Inputs: filter, filter_or, sort, reverse, +2 more.

list_user_groupsB

Henter liste over brugergrupper

Inputs: no named parameters.

list_usersB

Henter liste over alle brugere i systemet

Inputs: no named parameters.

update_objectB

Opdaterer et objekt i et modul

Inputs: module (required), data (required).

update_orderC

Opdaterer en eksisterende ordre

Inputs: order_id (required), name, description, deadline_date, +5 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 22 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for connecting Claude Desktop to FHIRfly healthcare reference data APIs, enabling lookup of drugs, providers, clinical codes, and more.
      71 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server giving Claude (and any MCP-compatible client) live access to SAP systems via ADT for reading, searching, editing, and activating ABAP objects.
      163 npm
      22
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that integrates with Microsoft Dynamics 365 Business Central, enabling querying of customers, items, and sales orders through natural language commands in Claude Desktop.
      10
      -
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for the ONE Framework ERP that enables Claude to explore data models, run queries, and understand business logic through autonomous access.
      10
      ISC