Tripletex MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRIPLETEX_API_URL | No | API base URL (default: https://tripletex.no/v2) | https://tripletex.no/v2 |
| TRIPLETEX_COMPANY_ID | No | Company ID (default: 0 = own company) | 0 |
| TRIPLETEX_CONSUMER_TOKEN | Yes | API consumer token | |
| TRIPLETEX_EMPLOYEE_TOKEN | Yes | Employee token |
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 |
|---|---|
| whoamiB | Get information about the currently authenticated user. |
| search_projectsB | Search for projects by name or other filters. Use this to find project IDs for logging hours. |
| search_activitiesB | Search for activities (e.g. development, meetings, vacation). Use this to find activity IDs for logging hours. |
| search_timesheet_entriesC | Search timesheet entries for a date range. Returns hours logged by employees. |
| get_timesheet_entryC | Get a single timesheet entry by ID. |
| create_timesheet_entryA | Create a new timesheet entry (log hours). Only one entry per employee/date/activity/project combo. |
| update_timesheet_entryC | Update an existing timesheet entry. Fields not set will be nulled. |
| delete_timesheet_entryB | Delete a timesheet entry. |
| get_total_hoursB | Get total hours registered for an employee in a date range. |
| get_recent_projectsC | Get recently used projects for timesheet entries. |
| get_recent_activitiesC | Get recently used activities for a project. |
| start_time_clockC | Start a time clock (timer) for tracking hours in real-time. |
| stop_time_clockC | Stop a running time clock. |
| get_current_time_clockC | Get the currently running time clock for an employee. |
| search_timesheet_weeksC | Search weekly timesheet status. |
| approve_timesheet_weekC | Approve a timesheet week. |
| complete_timesheet_weekC | Mark a timesheet week as complete. |
| reopen_timesheet_weekC | Reopen a completed/approved timesheet week. |
| get_timesheet_monthC | Get monthly timesheet status for employees. |
| approve_timesheet_monthC | Approve a timesheet month. |
| complete_timesheet_monthC | Mark a timesheet month as complete. |
| reopen_timesheet_monthC | Reopen a completed/approved timesheet month. |
| search_invoicesC | Search outgoing (customer) invoices by date range. |
| get_invoiceC | Get a single outgoing invoice by ID. |
| search_supplier_invoicesB | Search incoming (supplier) invoices by date range. |
| get_supplier_invoiceB | Get a single supplier invoice by ID. |
| get_supplier_invoices_for_approvalC | Get supplier invoices that are pending approval. |
| approve_supplier_invoiceC | Approve a supplier invoice. |
| approve_supplier_invoicesC | Approve multiple supplier invoices at once. |
| reject_supplier_invoiceB | Reject a supplier invoice. A comment is required. |
| reject_supplier_invoicesA | Reject multiple supplier invoices at once. A comment is required. |
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 31 tools
Most tools have distinct purposes, but there is some overlap between approve/reject supplier invoices (single vs. multiple) and timesheet month/week operations, which could cause minor confusion. The descriptions clarify the differences, so misselection is unlikely.
All tools follow a consistent verb_noun naming pattern (e.g., approve_supplier_invoice, get_timesheet_entry, search_activities). There are no deviations in style or convention, making the set predictable and readable.
With 31 tools, the count is borderline high for a timesheet and invoicing server, potentially feeling heavy. However, it covers multiple domains (timesheets, invoices, time clocks), so it's not extreme but may overwhelm agents.
The toolset provides comprehensive coverage for timesheet management (CRUD, approval, completion, reopening), supplier invoice handling (approval, rejection, search), and time clock operations. No obvious gaps exist for the stated purposes.