Skip to main content
Glama
EARLY App MCP Server

EARLY App MCP Server

by janfincke
README.md
# EARLY App MCP Server

[![npm version](https://img.shields.io/npm/v/@janfincke/early-mcp-server.svg)](https://www.npmjs.com/package/@janfincke/early-mcp-server)
[![Documentation](https://img.shields.io/badge/docs-mkdocs-blue.svg)](https://janfincke.github.io/early-mcp-server/)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
[![Node.js](https://img.shields.io/badge/Node.js-%3E%3D18.0.0-green.svg)](https://nodejs.org/)

An unofficial Model Context Protocol (MCP) server that provides access to the EARLY app time tracking public API.

## Overview

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.


### Tools

#### Time Entry Management

-   `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

#### Activity Management

-   `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

#### User & Reports

-   `generate_report` - Generate summary reports for time entries
-   `get_current_user` - Get current user information


### Resources

#### Time Entries

-   `early://time-entries/today` - Today's time entries with detailed JSON data
-   `early://time-entries/week` - Current week's time entries

#### Activities

-   `early://activities` - All activities (active + inactive + archived)
-   `early://activities/active` - Only active activities


## Quick Start

### Installation

No installation required! Use npx to run the server:

```bash
npx @janfincke/early-mcp-server
```

### Configuration (for Claude Desktop and others)


```json
{
  "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**

## Documentation

**[Complete Documentation](https://janfincke.github.io/early-mcp-server/)**

Comprehensive documentation is available at **[janfincke.github.io/early-mcp-server](https://janfincke.github.io/early-mcp-server/)** including:

- **[Getting Started Guide](https://janfincke.github.io/early-mcp-server/getting-started/)** - Installation and setup
- **[Tools Reference](https://janfincke.github.io/early-mcp-server/tools/)** - Complete documentation for all 6 tools
- **[Integration Guide](https://janfincke.github.io/early-mcp-server/integration/)** - Claude Desktop and MCP client setup
- **[Troubleshooting](https://janfincke.github.io/early-mcp-server/troubleshooting/)** - Common issues and solutions

### EARLY API Documentation

-   **Base URL**: https://developers.early.app/
-   **Documentation**: Postman Collection
-   **Authentication**: API Key (assumed)


## Contributing

1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Add tests
5. Submit a pull request

## License

MIT License - see LICENSE file for details.

TDQS

B3.2/5.0

Scored across 14 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues