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., "@EARLY App MCP Server Show today's time entries"
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.
An unofficial Model Context Protocol (MCP) server that provides access to the EARLY app time tracking public API.
EARLY is a time tracking application with a comprehensive public API. This MCP server enables AI assistants to interact with time tracking data through the public EARLY API.
create_time_entry - Create a new time entry with flexible time parameters
edit_time_entry - Edit an existing time entry
get_time_entries - Get time entries for a date range
delete_time_entry - Delete a time entry by ID
start_timer - Start tracking time for a project
stop_timer - Stop the currently running timer
get_active_timer - Get information about the currently running timer
update_active_timer - Update the description of the currently running timer
list_activities - Get all activities
create_activity - Create a new activity (project)
update_activity - Update an existing activity
archive_activity - Archive or delete an activity
generate_report - Generate summary reports for time entries
get_current_user - Get current user information
early://time-entries/today - Today's time entries with detailed JSON data
early://time-entries/week - Current week's time entries
early://activities - All activities (active + inactive + archived)
early://activities/active - Only active activities
Related MCP server: TimePRO MCP Server
No installation required! Use npx to run the server:
npx @janfincke/early-mcp-server{
"mcpServers": {
"early-time-tracker": {
"command": "npx",
"args": [
"@janfincke/early-mcp-server"
],
"env": {
"EARLY_API_KEY": "your-early-api-key-here",
"EARLY_API_SECRET": "your-early-api-secret-here"
}
}
}
}Get your API credentials from the EARLY desktop app: Settings → Developer → API Keys
Comprehensive documentation is available at janfincke.github.io/early-mcp-server including:
Getting Started Guide - Installation and setup
Tools Reference - Complete documentation for all 6 tools
Integration Guide - Claude Desktop and MCP client setup
Troubleshooting - Common issues and solutions
Base URL: https://developers.early.app/
Documentation: Postman Collection
Authentication: API Key (assumed)
Fork the repository
Create a feature branch
Make your changes
Add tests
Submit a pull request
MIT License - see LICENSE file for details.
Archive or delete an activity
Inputs: activityId (required).
Create a new activity (project)
Inputs: name (required), color, billable, clientId, +1 more.
Create a new time entry with flexible time parameters
Inputs: projectId (required), description (required), endTime, duration, +1 more.
Delete a time entry by ID
Inputs: timeEntryId (required).
Edit an existing time entry
Inputs: timeEntryId (required), endTime, startTime, activityId, +1 more.
Generate a summary report of time entries for a given period
Inputs: endDate (required), startDate (required), projectId.
Get information about the currently running timer
Inputs: no named parameters.
Get information about the currently authenticated user
Inputs: no named parameters.
Get time entries for a date range
Inputs: endDate, projectId, startDate.
Get all activities
Inputs: activeOnly.
Start tracking time for an activity
Inputs: projectId (required), description.
Stop the currently running timer
Inputs: no named parameters.
Update the description of the currently running timer
Inputs: description (required).
Update an existing activity
Inputs: activityId (required), name, color, billable, +3 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 14 tools
Most tools have clearly distinct purposes, especially around timers, time entries, and activities. There is some potential overlap between create_time_entry and start_timer, but the descriptions clarify the difference between completed entries and a running timer.
The tool names consistently use snake_case with a verb_noun pattern. Minor inconsistency appears in using edit_time_entry versus update_activity for similar edit/update operations.
With 14 tools, the set is well-scoped for a time-tracking and activity-management server. Each tool appears to earn its place without excessive surface area.
The server covers core workflows: user context, timers, time-entry CRUD, activity lifecycle, and reporting. Minor gaps exist, such as fetching a single activity by ID, but agents can work around them via list_activities.
MCP server exposing klokin time-tracking operations (employees, time entries, stores) to AI clients.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
MCP server that lets your AI assistant build and deploy apps, hosting each one at a live URL.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
