TMetric MCP Server
# TMetric MCP Server
Minimal Model Context Protocol server for TMetric time tracking integration.
## Features
- List TMetric projects
- Start/stop timers
- Check current timer status
- GitLab issue integration
- Delete time entries
## Installation
```bash
npm install
npm run build
```
## Configuration
Set your TMetric API token:
```bash
export TMETRIC_API_TOKEN="your_token_here"
```
## Usage with Claude Code
Add the TMetric MCP server using the `claude mcp add` command. You can install at different scopes:
### User Scope (Global - All Projects)
Available across all projects for your user:
**One-liner:**
```bash
claude mcp add --scope user tmetric-mcp --env TMETRIC_API_TOKEN=your_token_here -- node /path/to/tmetric-mcp-server/build/index.js
```
**Interactive:**
```bash
claude mcp add tmetric-mcp --scope user
```
When prompted, configure:
- **Command**: `node`
- **Args**: `/path/to/tmetric-mcp-server/build/index.js`
- **Environment variables**: `TMETRIC_API_TOKEN=your_token_here`
### Project Scope (Specific Project)
Available only in the current project directory:
**One-liner:**
```bash
claude mcp add --scope project tmetric-mcp --env TMETRIC_API_TOKEN=your_token_here -- node /path/to/tmetric-mcp-server/build/index.js
```
**Interactive:**
```bash
claude mcp add tmetric-mcp --scope project
```
When prompted, configure with the same settings as above.
### Local Scope (Current Directory)
Available only in the current working directory:
**One-liner:**
```bash
claude mcp add --scope local tmetric-mcp --env TMETRIC_API_TOKEN=your_token_here -- node /path/to/tmetric-mcp-server/build/index.js
```
**Interactive:**
```bash
claude mcp add tmetric-mcp --scope local
```
When prompted, configure with the same settings as above.
### Alternative: Using npx (from GitHub)
You can run directly from GitHub with npx (no clone or build needed):
**One-liner:**
```bash
claude mcp add --scope user tmetric-mcp --env TMETRIC_API_TOKEN=your_token_here -- npx -y github:guglielmo/tmetric-minimal-mcp
```
**Interactive:**
```bash
claude mcp add tmetric-mcp --scope user
```
When prompted, configure:
- **Command**: `npx`
- **Args**: `-y github:guglielmo/tmetric-minimal-mcp`
- **Environment variables**: `TMETRIC_API_TOKEN=your_token_here`
### Alternative: Using npx (from local path)
If you've cloned the repository locally:
**One-liner:**
```bash
claude mcp add --scope user tmetric-mcp --env TMETRIC_API_TOKEN=your_token_here -- npx -y /path/to/tmetric-mcp-server
```
**Interactive:**
```bash
claude mcp add tmetric-mcp --scope user
```
When prompted, configure:
- **Command**: `npx`
- **Args**: `-y /path/to/tmetric-mcp-server`
- **Environment variables**: `TMETRIC_API_TOKEN=your_token_here`
## Available Tools
### list_tmetric_projects()
Get list of available projects.
### get_current_timer()
Check if a timer is running.
### start_timer(project_id, task_name, task_url?)
Start tracking time on a project/task.
### stop_timer()
Stop current timer and return time spent.
### delete_time_entry(entry_id?)
Delete a time entry.
## Development
```bash
# Watch mode
npm run watch
# Run directly with tsx
npm run dev
```
## Testing
### Running Tests
```bash
# Run all tests once
npm test
# Run tests in watch mode (re-runs on file changes)
npm run test:watch
# Run tests with coverage report
npm run test:coverage
# Run tests with interactive UI
npm run test:ui
```
### Test Coverage
The project has comprehensive test coverage with:
- **100% statement coverage** across all modules
- **97%+ branch coverage** for edge cases
- Unit tests for all utility functions (`utils.ts`)
- Full integration tests for TMetric API client (`tmetric-client.ts`)
- Mocked HTTP requests using `nock` for reliable testing
See [TESTING.md](TESTING.md) for detailed information about the testing strategy and how to write new tests.
### Manual Testing
Test the MCP server with Claude Code by starting a conversation and using commands like:
- "List my TMetric projects"
- "Start timer on project 12345 for Issue #123: Fix bug"
- "What am I working on?"
- "Stop the timer"
## Troubleshooting
### "TMETRIC_API_TOKEN is required"
Make sure you've set the environment variable with your API token.
### "Failed to initialize TMetric client"
Check that your API token is valid and you have network access to TMetric.
### "Timer already running"
This is expected behavior. Stop the current timer before starting a new one.
## Used By
This MCP server is a dependency for the following Claude Code skills:
- **[issue-time-tracking](../../skills/issue-time-tracking/)** - Automates synchronized issue status tracking and time logging across GitLab/GitHub and TMetric
## License
MITTDQS
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.