mite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MITE_MODE | No | Server mode: read-only, write or admin | read-only |
| MITE_TOOLS | No | Comma-separated allowlist, e.g. mite_report_projects_by_month | |
| MITE_ACCOUNT | Yes | Account name — the subdomain of https://<account>.mite.de | |
| MITE_API_KEY | Yes | Your personal mite API key | |
| MITE_ALLOW_ADMIN | No | true = mode admin; alternative to MITE_MODE | |
| MITE_ALLOW_WRITE | No | true = mode write; alternative to MITE_MODE |
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 |
|---|---|
| mite_whoamiA | Shows the mite account, the user behind the API key and its role, plus the mode and tools this server offers. Call it first to learn what you are allowed to do; for projects use |
| mite_report_projects_by_monthA | Aggregated report from mite: hours and revenue per project and month for a period, grouped on the mite server so whole years work without reading single entries. For other groupings or totals use |
| mite_reportA | Aggregated report from mite: hours, revenue and share of hours, grouped by 1 to 3 of customer, project, service, user, day, week, month, year for a period, on the mite server so whole years work. For the fixed project-by-month view use |
| mite_report_budgetA | Budget, consumption, remaining budget and percent used per project over the whole project life, not for a period; for hours or revenue in a period use |
| mite_report_billable_ratioA | Billable hours, non-billable hours and the billable share in percent for a period, optionally per customer, project, user, month, aggregated on the mite server. For revenue or other groupings use |
| mite_list_time_entriesA | Lists single time entries from mite for a period, newest first, optionally filtered by customer, project, service, user, billable or locked. Use it to find individual entries or their ids; for totals use |
| mite_get_time_entryA | Fetches one time entry from mite by its id; use it when the id is known, otherwise find entries with |
| mite_tracker_statusA | Tells whether the mite time tracker is currently running for the key's user and, if so, on which time entry. Returns |
| mite_list_customersA | Lists customers from mite, active ones or with |
| mite_list_projectsA | Lists projects from mite, active ones or with |
| mite_list_servicesA | Lists services (activity types) from mite, active ones or with |
| mite_list_usersA | Lists users from mite, active ones or with |
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 12 tools
Most tools target distinct operations; the main ambiguity is among the four report tools, but descriptions explicitly route between them (fixed project-by-month, flexible grouping, budget, billable ratio). `mite_list_projects` also exposes budget fields while `mite_report_budget` handles budget usage, but the boundary is stated.
Names use a consistent `mite_` prefix and snake_case, mostly following a verb_noun pattern such as `list_time_entries`, `get_time_entry`, and `report_budget`. Minor deviations are `whoami`, bare `report`, and `tracker_status`, but they remain readable and predictable.
Twelve tools is well within the ideal range and each supports a clear part of the read/report workflow: identity, reference lists, time entries, tracker status, and aggregations. No obvious redundant filler.
The surface covers read-only lookups and reporting well, including time entries, reference data, budgets, and billable ratios. However, there are no create/update/delete operations for time entries and no start/stop tracker controls, so lifecycle coverage is notably incomplete if the server is meant to support time tracking rather than only reporting.