MCP Server for Visma Intempus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_TOKEN | Yes | Shared token with the gateway for HTTP authentication. | |
| INTEMPUS_API_KEY | Yes | Intempus API key. | |
| INTEMPUS_PROFILE | Yes | Profile to run: employee, approver, or admin. | |
| INTEMPUS_API_USER | Yes | Intempus API username (case-sensitive). | |
| INTEMPUS_AUDIT_LOG | Yes | Path to the audit log file (e.g., /data/audit.jsonl). | |
| INTEMPUS_DEFAULT_USER | No | Default acting user for stdio mode (e.g., you@example.com). | |
| INTEMPUS_IDENTITY_MAP | No | Mapping of Entra UPN to Intempus username or work email. | |
| INTEMPUS_ENABLE_WRITES | Yes | Enable write operations. Set to 'true' in production. | |
| INTEMPUS_OPERATION_SECRET | No | Secret for HMAC signing of prepared operations. Required for the admin profile. | |
| INTEMPUS_TRUST_FORWARDED_USER | Yes | Whether to trust the X-MCP-User header forwarded by the gateway. Set to 'true' in production. | |
| INTEMPUS_APPROVER_UNASSIGNED_SCOPE | No | Set to 'all' to allow approvers without assignments to see all employees. |
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 |
|---|---|
| intempus_search_capabilitiesA | Search the Intempus MCP server capabilities and examples. Use this first when deciding which tool to call. |
| intempus_whoamiB | Show this endpoint's profile and the Intempus employee (and approver levels) the session is bound to. |
| intempus_list_casesB | Search cases/projects that accept time registrations, by number, name or customer. |
| intempus_list_work_typesA | Work types (projekttimer, ferie, sygdom, kørsel …). Employees and approvers get the types of their own work model; admins may filter by work model or employee. |
| intempus_get_my_profileA | Your Intempus employee record, contracts (work model, locked date) and approver levels. |
| intempus_list_my_work_reportsB | Your time registrations in a period (default: last 31 days), with approval status and total. |
| intempus_register_timeA | Register time for yourself. Give a work type, optional case, a date and either startTime+endTime (optionally breakHours) or hours. Checks that you have a contract on the date, that the work type belongs to your work model and that the case is open. Pass idempotencyKey to make a retry safe. |
| intempus_update_my_work_reportA | Change one of your own time registrations. Only possible while it is neither approved nor locked. |
| intempus_delete_my_work_reportA | Delete one of your own time registrations. Only possible while it is neither approved nor locked. |
| intempus_get_my_balancesA | Your balances (ferie, feriefri, timebank/flex, sygdom …) as computed by Intempus up to a date (default today). Holiday accrues at month end, so pass to = the end of the holiday year to see the full entitlement. Only balances visible to employees. |
| intempus_get_my_planningC | Your planned work in a period (default: the next 14 days). |
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 11 tools
Most tools have clearly distinct purposes (list work types, list cases, register/update/delete time, balances, planning). However, intempus_whoami and intempus_get_my_profile overlap in showing employee/approver info, which could cause an agent to pick the wrong one.
All tools use the intempus_ prefix and snake_case, with a mostly consistent verb_noun pattern (list_work_types, get_my_balances, register_time). The outlier is intempus_whoami, which does not follow the verb_noun format, but this is a common exception.
11 tools is well within the ideal range and each tool maps to a distinct operation within the employee self-service domain (time registration CRUD, profiles, balances, planning). No tool feels redundant or missing at the count level.
Core employee workflows are covered: time registration create/read/update/delete, work types, cases, balances, and planning. Approver-specific operations (e.g., approving/rejecting reports) are absent despite approver levels being mentioned, and there is no single-report retrieval, but these are minor workable gaps.