EARLY App MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EARLY_API_KEY | Yes | Your EARLY API key | |
| EARLY_API_SECRET | Yes | Your EARLY API secret |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_time_entryC | Create a new time entry with flexible time parameters |
| get_time_entriesB | Get time entries for a date range |
| edit_time_entryC | Edit an existing time entry |
| delete_time_entryC | Delete a time entry by ID |
| list_activitiesC | Get all activities |
| create_activityB | Create a new activity (project) |
| update_activityC | Update an existing activity |
| archive_activityC | Archive or delete an activity |
| generate_reportB | Generate a summary report of time entries for a given period |
| get_current_userA | Get information about the currently authenticated user |
| start_timerC | Start tracking time for an activity |
| stop_timerA | Stop the currently running timer |
| get_active_timerA | Get information about the currently running timer |
| update_active_timerA | Update the description of the currently running timer |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| today_time_entries | Time entries for today |
| week_time_entries | Time entries for current week |
| all_activities | List of all activities |
| active_activities | List of active activities only |
TDQS
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.