Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MITE_MODENoServer mode: read-only, write or adminread-only
MITE_TOOLSNoComma-separated allowlist, e.g. mite_report_projects_by_month
MITE_ACCOUNTYesAccount name — the subdomain of https://<account>.mite.de
MITE_API_KEYYesYour personal mite API key
MITE_ALLOW_ADMINNotrue = mode admin; alternative to MITE_MODE
MITE_ALLOW_WRITENotrue = 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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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_list_projects, for customers mite_list_customers. Returns account name, title and currency, the user id, name and role, and the server mode with the names of all enabled tools. Takes no input and is available in every mode.

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_report; for single entries use mite_list_time_entries. Returns rows of month (YYYY-MM), project, hours and revenue in currency units plus a total; revenue is null without rates. Read-only, no paging, default period is this year.

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_projects_by_month, for billable share use mite_report_billable_ratio, for budgets use mite_report_budget. Returns rows with hours, revenue in currency units (null without rates) and share of hours in percent, plus a total. Read-only, no paging, default period is this year.

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. Minute budgets are in hours, cent budgets in currency units (consumption = revenue); budget, remaining and percent are null for projects without a budget. Without project_id: all active projects with a budget. Read-only, no paging.

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_report. Returns hours and a ratio in percent with one decimal, per group and as a total. Read-only, no paging, default period is this year.

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_report, for one known entry use mite_get_time_entry. Each row has hours, revenue in currency units (null if none), the locked flag and the note. Returns at most limit entries per page (default 100, max 1000) and has_more when further pages exist; the period defaults to this_year.

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_list_time_entries. Returns date, hours, revenue in currency units (null if none), billable and locked flags, customer, project, service, user and note. Fails with "not found" if no time entry has this id.

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 running and, when it runs, time_entry_id, the start time since and minutes, the entry's total so far in minutes. Read-only and takes no input; to look at that entry in full use mite_get_time_entry.

mite_list_customersA

Lists customers from mite, active ones or with archived: true the archived ones; use it to look up customer ids for filters such as customer_id in mite_list_time_entries. Returns id, name, archived flag and note per customer. The whole list is returned at once without paging.

mite_list_projectsA

Lists projects from mite, active ones or with archived: true the archived ones; use it to look up project ids for filters such as project_id in mite_list_time_entries, for budget usage use mite_report_budget. Returns id, name, customer, archived flag, note, budget and budget_type; budget is in the unit given by budget_type (minutes or cents), not hours or currency units. The whole list is returned at once without paging.

mite_list_servicesA

Lists services (activity types) from mite, active ones or with archived: true the archived ones; use it to look up service ids for filters such as service_id in mite_list_time_entries. Returns id, name, billable flag, archived flag and note per service. The whole list is returned at once without paging.

mite_list_usersA

Lists users from mite, active ones or with archived: true the archived ones; use it to look up user ids for user_id in mite_list_time_entries, and mite_whoami for the current user. Returns id, name, role and archived flag per user; email addresses and hourly rates are not returned. The whole list is returned at once without paging.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 12 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness3/5

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.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive