Tracker MCP Server
Click on "Deploy 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., "@Tracker MCP Servershow today's schedule"
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.
Tracker MCP Server
This is an MCP (Model Context Protocol) server designed to connect to your local tracker-server. It exposes endpoints like checking and applying today's schedule, retrieving statistics, registering tasks, and managing timers directly to LLM clients (like Claude Desktop or Cursor).
Prerequisites
A running instance of
tracker-server(usually onhttp://localhost:3000).Python 3.11+ (if running locally) or Docker.
Related MCP server: mcp-server-tasktracker
🚀 Running via Docker (Recommended)
When you deploy your MCP agent, you can hook it directly to the Docker image provided from the GitHub Container Registry.
Because tracker-server is running on your host machine locally, Docker needs to know how to reach it. The image defaults to http://host.docker.internal:3000 assuming you are on Mac/Windows or using Docker Desktop.
For Claude Desktop configuration (claude_desktop_config.json):
{
"mcpServers": {
"tracker-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TRACKER_API_URL=http://host.docker.internal:3000",
"ghcr.io/egormak/tracker-mcp:sha-57577b3"
]
}
}
}Note: Notice the
-iflag. Because MCP communicates over stdin/stdout (stdio), you must run the docker container interactively, but without a TTY (-t).
🛠Running Locally
If you are developing or simply prefer to run from source instead of Docker.
Setup the Virtual Environment:
cd tracker-mcp python -m venv venv source venv/bin/activate pip install -r requirements.txtRun the MCP Server manually:
# Make sure your tracker server is running! python server.pyNote: This will just block your terminal waiting for
stdioMCP JSON RPC commands. This is expected.Configure Claude Desktop (Local Mode):
{ "mcpServers": { "tracker-mcp": { "command": "/absolute/path/to/tracker-mcp/venv/bin/python", "args": [ "/absolute/path/to/tracker-mcp/server.py" ], "env": { "TRACKER_API_URL": "http://localhost:3000" } } } }
This server cannot be deployed
Maintenance
Related MCP Connectors
- mcp-serverOAuthio.klokin
MCP server exposing klokin time-tracking operations (employees, time entries, stores) to AI clients.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Track Keito time entries and LLM costs from AI agents.
MCP server providing access to the Scorecard API to evaluate and optimize LLM systems.
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server that enables LLM clients to manage tasks, timers, and notes in Rhizm through natural language commands. It provides tools for task operations, time tracking, and note management via API integration.114 npmMIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that exposes the full Task-Tracker REST API as MCP tools, enabling AI agents to manage trackers, tasks, notes, checklists, and projects conversationally.MIT
- AlicenseBqualityCmaintenanceEnables AI clients to create and manage tasks via a local REST API by converting natural language into HTTP requests through the Model Context Protocol.1MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that lets LLMs interact with your Clockify workspace for time-tracking automation and reporting, enabling natural language logging of time entries, querying entries, and generating reports.MIT