TMetric MCP Server
Integrates with GitLab issues to enable time tracking linked to issues, allowing start/stop timers and sync time entries.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@TMetric MCP ServerStart a timer for GitLab issue #45 on project Alpha"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Related MCP server: Tempo MCP Server
Installation
npm install
npm run buildConfiguration
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.jsInteractive:
claude mcp add tmetric-mcp --scope userWhen prompted, configure:
Command:
nodeArgs:
/path/to/tmetric-mcp-server/build/index.jsEnvironment 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.jsInteractive:
claude mcp add tmetric-mcp --scope projectWhen 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.jsInteractive:
claude mcp add tmetric-mcp --scope localWhen 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-mcpInteractive:
claude mcp add tmetric-mcp --scope userWhen prompted, configure:
Command:
npxArgs:
-y github:guglielmo/tmetric-minimal-mcpEnvironment 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-serverInteractive:
claude mcp add tmetric-mcp --scope userWhen prompted, configure:
Command:
npxArgs:
-y /path/to/tmetric-mcp-serverEnvironment 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 devTesting
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:uiTest 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
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/guglielmo/tmetric-minimal-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server