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_entryB | Create a new time entry with flexible time parameters |
| get_time_entriesB | Get time entries for a date range |
| edit_time_entryB | Edit an existing time entry |
| delete_time_entryA | Delete a time entry by ID |
| list_activitiesB | Get all activities |
| create_activityA | 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_timerB | 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
Each tool targets a distinct action on a specific resource (activities, time entries, timer, user). No two tools have overlapping purposes, and descriptions clearly differentiate them.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_activity, start_timer). No mixing of conventions.
14 tools cover the core operations for a time-tracking and activity management server without being excessive. Each tool serves a clear function.
The set covers CRUD for activities and time entries, plus timer management and reporting. Missing individual get-by-ID tools (e.g., get_activity, get_time_entry) but these are minor gaps that agents can work around.