TMetric MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TMETRIC_API_TOKEN | Yes | Your TMetric API 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tmetric_projectsA | Get list of available TMetric projects for time tracking |
| get_current_timerA | Check if a timer is currently running and get its details |
| start_timerA | Start time tracking on a project and task. Will fail if another timer is already running. |
| stop_timerA | Stop the currently running timer and return time spent |
| delete_time_entryA | Delete a time entry. Mode "current" deletes active timer only, "last" deletes most recent entry (with 5-min safety window). |
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 5 tools
Each tool has a clearly distinct purpose: listing projects, checking the current timer, starting, stopping, and deleting time entries. There is no overlap or ambiguity between them.
Most tools follow a consistent verb_noun pattern (list, get, start, stop, delete). The only inconsistency is 'list_tmetric_projects' including the server name, unlike the others, which is minor and doesn't harm readability.
With 5 tools, the server is well-scoped for its purpose of time tracking. Each tool covers a core operation without unnecessary bloat, making it easy to navigate.
The server covers the basic timer lifecycle (start, stop, check, delete) and project listing, but lacks the ability to list past time entries or fetch tasks for a project, which are common needs. These gaps could hinder an agent from effectively managing time tracking.