Skip to main content
Glama
sakebomb

Early MCP

by sakebomb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EARLY_API_KEYYesAn EARLY developer API key
EARLY_API_SECRETYesAn EARLY developer 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_activitiesB

List all activities in EARLY.

Returns the full list of activities with their IDs, names, colors, etc.

create_activityB

Create a new activity in EARLY.

Args:
    name: Name of the activity (e.g. "Deep Work", "Meetings")
    color: Hex color code for the activity (default: green)
update_activityC

Update an existing activity in EARLY.

Args:
    activity_id: ID of the activity to update
    name: New name for the activity (optional)
    color: New hex color code (optional)
delete_activityB

Archive/delete an activity in EARLY.

Args:
    activity_id: ID of the activity to archive
current_trackingA

Get the currently running tracking entry, if any.

Returns the active timer with activity info and start time, or an error with "does not exist" if nothing is tracking.

start_trackingA

Start tracking time for an activity.

Args:
    activity_id: ID of the activity to track (use list_activities to find IDs)
    note: Optional note/description for this tracking session
stop_trackingA

Stop the currently running tracker.

Returns the completed time entry with start/stop times and duration.

list_time_entriesB

Query time entries within a date range.

Args:
    start_date: Start date in YYYY-MM-DD format (e.g. "2026-02-01")
    end_date: End date in YYYY-MM-DD format (e.g. "2026-02-16")
create_time_entryA

Create a manual time entry.

Args:
    activity_id: ID of the activity
    started_at: Start time in ISO format (e.g. "2026-02-16T09:00:00.000")
    stopped_at: Stop time in ISO format (e.g. "2026-02-16T10:30:00.000")
    note: Optional note/description for this entry
delete_time_entryC

Delete a time entry.

Args:
    entry_id: ID of the time entry to delete
time_summaryA

Aggregate hours by activity for a time period.

Args:
    period: One of "today", "yesterday", "week", "last_week", "month", "last_month"
efficiency_reportA

Analyze time distribution and detect gaps between entries.

Shows how time was spent, identifies untracked gaps, and provides
daily breakdowns. Useful for finding productivity patterns.

Args:
    start_date: Start date in YYYY-MM-DD format
    end_date: End date in YYYY-MM-DD format
billing_reportB

Calculate billable hours and cost by activity.

Args:
    start_date: Start date in YYYY-MM-DD format
    end_date: End date in YYYY-MM-DD format
    hourly_rate: Rate per hour in your currency
explore_apiA

Make a raw authenticated request to any EARLY API endpoint.

Use this to probe undocumented or newly discovered endpoints.
The base URL is already set — just provide the path.

Args:
    method: HTTP method (GET, POST, PATCH, DELETE, PUT)
    path: API path (e.g. "/tracking", "/time-entries/2024-01-01/2024-01-31")
    body: JSON request body (optional)
    params: Query parameters (optional)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 14 tools

Disambiguation5/5

Each tool targets a distinct resource or action: activities, time entries, tracking state, reports, and raw API access. No functional overlap; descriptions clearly differentiate them.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_activity, list_time_entries, stop_tracking). No mixed conventions or ambiguous verbs.

Tool Count5/5

14 tools cover the full scope of a time-tracking server: CRUD for activities and entries, tracking controls, multiple reports, and an API explorer. Well-balanced, not excessive or sparse.

Completeness4/5

Core lifecycle is covered: create/read/update/delete activities, create/delete/list time entries, start/stop/current tracking. Minor gaps: no update_time_entry or get_single_time_entry, but workflows are still functional.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources