TMetric MCP Server
Integrates with TMetric for time tracking, enabling project listing, timer start/stop, and deletion of entries, with GitLab issue support.
README
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
npm install
npm run build
Configuration
Set your TMetric API token:
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:
claude mcp add --scope user tmetric-mcp --env TMETRIC_API_TOKEN=your_token_here -- node /path/to/tmetric-mcp-server/build/index.js
Interactive:
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:
claude mcp add --scope project tmetric-mcp --env TMETRIC_API_TOKEN=your_token_here -- node /path/to/tmetric-mcp-server/build/index.js
Interactive:
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:
claude mcp add --scope local tmetric-mcp --env TMETRIC_API_TOKEN=your_token_here -- node /path/to/tmetric-mcp-server/build/index.js
Interactive:
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:
claude mcp add --scope user tmetric-mcp --env TMETRIC_API_TOKEN=your_token_here -- npx -y github:guglielmo/tmetric-minimal-mcp
Interactive:
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:
claude mcp add --scope user tmetric-mcp --env TMETRIC_API_TOKEN=your_token_here -- npx -y /path/to/tmetric-mcp-server
Interactive:
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
# Watch mode
npm run watch
# Run directly with tsx
npm run dev
Testing
Running Tests
# 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
nockfor reliable testing
See 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 - Automates synchronized issue status tracking and time logging across GitLab/GitHub and TMetric
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.