Skip to main content
Glama

@everhour/mcp-server

npm version License: MIT

Complete Everhour API integration for Model Context Protocol (MCP) with 100% endpoint coverage

A comprehensive MCP server that provides seamless integration with the Everhour API, enabling AI assistants like Claude to manage time tracking, projects, tasks, and team productivity workflows.

šŸš€ Quick Start

Installation

# Using npx (recommended)
npx @everhour/mcp-server

# Or install globally
npm install -g @everhour/mcp-server
everhour-mcp-server

Prerequisites

Configuration

Set your Everhour API key as an environment variable:

export EVERHOUR_API_KEY=\"your_api_key_here\"

Related MCP server: Clockify MCP Server

šŸ“‹ MCP Client Setup

Claude Desktop

Add to your Claude Desktop configuration:

{
  \"mcpServers\": {
    \"everhour\": {
      \"command\": \"npx\",
      \"args\": [\"@everhour/mcp-server\"],
      \"env\": {
        \"EVERHOUR_API_KEY\": \"your_api_key_here\"
      }
    }
  }
}

Other MCP Clients

For other MCP-compatible clients, use:

# Command
npx @everhour/mcp-server

# Environment Variables
EVERHOUR_API_KEY=your_api_key_here

✨ Features

šŸŽÆ 100% API Coverage

All 37 available Everhour API endpoints implemented as MCP tools

šŸ›  Complete Functionality

  • Project Management: Create, update, list, and delete projects

  • Task Management: Full CRUD operations with estimates and time logging

  • Time Tracking: Comprehensive time record management

  • Timer Control: Start, stop, and monitor active timers

  • Client Management: Manage clients and business details

  • Section Organization: Project section management

  • Team Collaboration: User and team member management

šŸ”§ Developer-Friendly

  • TypeScript: Full type safety and IntelliSense support

  • Input Validation: Comprehensive validation with detailed error messages

  • Human-Readable: Time formats like "2h 30m" alongside seconds

  • Error Handling: Graceful error handling with helpful messages

šŸ”§ Available Tools (37 total)

  • everhour_list_projects - List all projects with filtering options

  • everhour_get_project - Get details of a specific project

  • everhour_create_project - Create a new project

  • everhour_update_project - Update project details

  • everhour_delete_project - Delete a project

Core Task Management:

  • everhour_list_tasks - List tasks with filtering by project, status, assignee

  • everhour_get_task - Get details of a specific task

  • everhour_create_task - Create a new task

  • everhour_update_task - Update task details

  • everhour_delete_task - Delete a task

Extended Task Features:

  • everhour_get_tasks_for_project - Get all tasks for specific project

  • everhour_update_task_estimate - Update task estimate

  • everhour_delete_task_estimate - Delete task estimate

  • everhour_add_time_to_task - Add time directly to task

  • everhour_update_task_time - Update task time

  • everhour_delete_task_time - Delete time from task

  • everhour_list_time_records - List time records with date/project filtering

  • everhour_get_time_record - Get details of a specific time record

  • everhour_create_time_record - Log time (supports human-readable formats)

  • everhour_update_time_record - Update existing time records

  • everhour_delete_time_record - Delete a time record

Core Timer Functions:

  • everhour_get_current_timer - Get the currently running timer

  • everhour_start_timer - Start a new timer

  • everhour_stop_timer - Stop the current timer

  • everhour_list_timers - List timer history

  • everhour_timer_status - Get timer status summary

Extended Timer Features:

  • everhour_get_running_timer - Get running timer (alternative endpoint)

  • everhour_start_timer_for_task - Start timer directly for specific task

  • everhour_list_clients - List all clients

  • everhour_get_client - Get details of a specific client

  • everhour_create_client - Create a new client

  • everhour_update_client - Update client details

  • everhour_delete_client - Delete a client

  • everhour_list_all_sections - List all sections (global search)

  • everhour_get_section - Get details of a specific section

  • everhour_create_section - Create a new section

  • everhour_update_section - Update section details

  • everhour_delete_section - Delete a section

  • everhour_get_current_user - Get current user profile

  • everhour_list_team_users - List all team users

  • everhour_get_user - Get details of a specific team user

šŸ“š Examples

Starting a Timer

{
  \"tool\": \"everhour_start_timer_for_task\",
  \"arguments\": {
    \"taskId\": \"task_123\",
    \"comment\": \"Working on user authentication feature\"
  }
}

Logging Time

{
  \"tool\": \"everhour_create_time_record\",
  \"arguments\": {
    \"time\": \"2h 30m\",
    \"date\": \"2024-01-15\",
    \"task\": \"task_123\",
    \"comment\": \"Implemented login functionality and wrote tests\"
  }
}

Creating a Project

{
  \"tool\": \"everhour_create_project\",
  \"arguments\": {
    \"name\": \"Mobile App Development\",
    \"client\": 456,
    \"type\": \"board\",
    \"billing\": {
      \"type\": \"hourly_rate\",
      \"rate\": 85.00
    }
  }
}

Getting Project Tasks

{
  \"tool\": \"everhour_get_tasks_for_project\",
  \"arguments\": {
    \"projectId\": \"proj_789\",
    \"status\": \"open\"
  }
}

šŸ• Time Format Support

The server supports flexible time input formats:

  • Human-readable: \"2h 30m\", \"90m\", \"1h 30m 45s\"

  • Minutes only: \"90m\" (90 minutes)

  • Seconds: 3600 (1 hour in seconds)

šŸ”§ Environment Variables

Variable

Required

Default

Description

EVERHOUR_API_KEY

āœ… Yes

-

Your Everhour API key

EVERHOUR_API_BASE_URL

āŒ No

https://api.everhour.com

API base URL

EVERHOUR_READONLY_MODE

āŒ No

false

Enable readonly mode for safety

šŸ”’ Readonly Mode

Readonly mode provides an additional security layer by blocking all write and delete operations, allowing only safe read operations.

When to Use Readonly Mode

  • Production environments where data integrity is critical

  • Reporting and analytics use cases

  • Shared or untrusted environments

  • Testing and development with live data

  • Compliance requirements for read-only access

Enabling Readonly Mode

# Via environment variable
EVERHOUR_READONLY_MODE=true npx @everhour/mcp-server

# Or export for session
export EVERHOUR_READONLY_MODE=true
npx @everhour/mcp-server

Claude Desktop Readonly Configuration

{
  "mcpServers": {
    "everhour-readonly": {
      "command": "npx",
      "args": ["@everhour/mcp-server"],
      "env": {
        "EVERHOUR_API_KEY": "your_api_key_here",
        "EVERHOUR_READONLY_MODE": "true"
      }
    }
  }
}

What's Blocked in Readonly Mode

  • āŒ Creating: Projects, tasks, clients, sections, time records

  • āŒ Updating: Any modifications to existing data

  • āŒ Deleting: Removal of any resources

  • āŒ Timer Control: Starting/stopping timers

  • āŒ Time Logging: Adding or modifying time entries

What's Allowed in Readonly Mode

  • āœ… Listing: All list operations (everhour_list_*)

  • āœ… Reading: All get operations (everhour_get_*)

  • āœ… Status Checks: Timer status, user information

  • āœ… Searching: Project, task, and client searches

  • āœ… Reports: Time record queries and analytics

Readonly Mode Status

When the server starts, it will log the current mode:

šŸ”’ EVERHOUR MCP SERVER - READONLY MODE ACTIVE
   Available tools: 19/37
   Blocked tools: 18 (write/delete operations)
   To enable full mode: Set EVERHOUR_READONLY_MODE=false

Or in full mode:

šŸ”“ EVERHOUR MCP SERVER - FULL MODE ACTIVE
   All 37 tools available
   To enable readonly mode: Set EVERHOUR_READONLY_MODE=true

šŸ“– Documentation

šŸ›  Development

Local Development

# Clone repository
git clone https://github.com/yourusername/everhour-mcp-server.git
cd everhour-mcp-server

# Install dependencies
npm install

# Set environment variables
cp .env.example .env
# Edit .env with your API key

# Development mode
npm run dev

# Build
npm run build

# Run built version
npm start

Project Structure

src/
ā”œā”€ā”€ api/
│   └── everhour-client.ts    # Everhour API client
ā”œā”€ā”€ tools/
│   ā”œā”€ā”€ clients.ts            # Client management tools
│   ā”œā”€ā”€ projects.ts           # Project management tools
│   ā”œā”€ā”€ tasks.ts              # Task management tools
│   ā”œā”€ā”€ task-extensions.ts    # Extended task features
│   ā”œā”€ā”€ time-records.ts       # Time record tools
│   ā”œā”€ā”€ timers.ts             # Timer control tools
│   ā”œā”€ā”€ sections.ts           # Section management tools
│   └── users.ts              # User management tools
ā”œā”€ā”€ types/
│   └── everhour.ts           # TypeScript type definitions
└── index.ts                  # MCP server entry point

Scripts

  • npm run dev - Development mode with auto-reload

  • npm run build - Build TypeScript to JavaScript

  • npm start - Start the built server

  • npm run lint - Run ESLint

  • npm run lint:fix - Fix ESLint issues

  • npm run clean - Clean build directory

šŸ¤ Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

  1. Fork the repository

  2. Create your feature branch (git checkout -b feature/amazing-feature)

  3. Commit your changes (git commit -m 'Add some amazing feature')

  4. Push to the branch (git push origin feature/amazing-feature)

  5. Open a Pull Request

šŸ“„ License

This project is licensed under the MIT License - see the LICENSE file for details.

šŸ“ž Support

šŸ† Features

  • āœ… Complete API Coverage - All 37 Everhour endpoints

  • āœ… Type Safety - Full TypeScript implementation

  • āœ… Input Validation - Comprehensive validation with Zod

  • āœ… Error Handling - Graceful error handling

  • āœ… Human-Readable - Time formats and clear responses

  • āœ… Well-Documented - Extensive documentation and examples

  • āœ… Production-Ready - Robust and reliable implementation


Made with ā¤ļø for the Model Context Protocol community

Available Tools

41 tools
everhour_add_time_to_taskC

Add time directly to a specific task using the /tasks/{id}/time endpoint.

Inputs: id (required), date (required), time (required), comment.

everhour_create_clientB

Create a new client in Everhour.

Inputs: name (required), businessDetails.

everhour_create_projectC

Create a new project in Everhour.

Inputs: name (required), type, client, billing.

everhour_create_sectionB

Create a new section in Everhour.

Inputs: name (required), project (required), position.

everhour_create_taskC

Create a new task in Everhour.

Inputs: name (required), project (required), type, labels, +3 more.

everhour_create_time_recordC

Create a new time record in Everhour. Time can be specified in seconds or human-readable format (e.g., "1h 30m", "90m", "5400s").

Inputs: date (required), time (required), task, comment, +1 more.

everhour_delete_clientA

Delete a client from Everhour. This action cannot be undone.

Inputs: id (required).

everhour_delete_projectA

Delete a project from Everhour. This action cannot be undone.

Inputs: id (required).

everhour_delete_sectionA

Delete a section from Everhour. This action cannot be undone.

Inputs: id (required).

everhour_delete_taskA

Delete a task from Everhour. This action cannot be undone.

Inputs: id (required).

everhour_delete_task_estimateA

Delete the estimate from a specific task.

Inputs: id (required).

everhour_delete_task_timeC

Delete time from a specific task using the /tasks/{id}/time endpoint.

Inputs: id (required).

everhour_delete_time_recordA

Delete a time record from Everhour. This action cannot be undone.

Inputs: id (required).

everhour_get_clientA

Get details of a specific client by ID.

Inputs: id (required).

everhour_get_current_timerA

Get the currently running timer, if any.

Inputs: no named parameters.

everhour_get_current_userA

Get the current user profile using the /me endpoint.

Inputs: no named parameters.

everhour_get_projectA

Get details of a specific project by ID.

Inputs: id (required).

everhour_get_running_timerA

Get the currently running timer using the /timer/running endpoint.

Inputs: no named parameters.

everhour_get_sectionA

Get details of a specific section by ID.

Inputs: id (required).

everhour_get_taskA

Get details of a specific task by ID.

Inputs: id (required).

everhour_get_tasks_for_projectB

Get all tasks for a specific project using the /tasks/for_project/{project_id} endpoint.

Inputs: projectId (required), page, limit, query, +2 more.

everhour_get_time_recordA

Get details of a specific time record by ID.

Inputs: id (required).

everhour_get_user_timeA

Get time records for a specific user with date range and pagination support.

Inputs: userId (required), to, from, page, +1 more.

everhour_list_all_sectionsA

List all sections from Everhour by iterating through all projects. Supports pagination and search query.

Inputs: page, limit, query.

everhour_list_clientsA

List all clients from Everhour. Supports pagination and search query.

Inputs: page, limit, query.

everhour_list_projectsA

List all projects from Everhour. Supports filtering by status, client, and search query.

Inputs: page, limit, query, client, +1 more.

everhour_list_tasksB

Search tasks from Everhour. Requires either a query or project parameter. Supports filtering by status, project, assignee, and search query.

Inputs: page, limit, query, status, +2 more.

everhour_list_team_usersA

List all team users using the /team/users endpoint. Supports selective property filtering via props parameter.

Inputs: props.

everhour_list_time_recordsA

List time records from Everhour. Supports filtering by project, assignee, and date range.

Inputs: to, from, page, limit, +2 more.

everhour_list_timersC

List timer history from Everhour. Supports filtering by project, assignee, and date range.

Inputs: to, from, page, limit, +2 more.

everhour_start_timerC

Start a new timer in Everhour. Can be associated with a task or project.

Inputs: task, comment, project.

everhour_start_timer_for_taskA

Start a timer directly for a specific task using the /timer/start_for/{task_id} endpoint.

Inputs: taskId (required), comment.

everhour_stop_timerA

Stop the currently running timer.

Inputs: no named parameters.

everhour_timer_statusC

Get a summary of timer status and activity.

Inputs: no named parameters.

everhour_update_clientB

Update an existing client in Everhour.

Inputs: id (required), name, businessDetails.

everhour_update_projectC

Update an existing project in Everhour.

Inputs: id (required), name, status, billing.

everhour_update_sectionB

Update an existing section in Everhour.

Inputs: id (required), name, position.

everhour_update_taskC

Update an existing task in Everhour.

Inputs: id (required), name, type, labels, +3 more.

everhour_update_task_estimateB

Update the estimate for a specific task.

Inputs: id (required), estimate (required).

everhour_update_task_timeC

Update time for a specific task using the /tasks/{id}/time endpoint.

Inputs: id (required), date, time, comment.

everhour_update_time_recordA

Update an existing time record in Everhour. Time can be specified in seconds or human-readable format.

Inputs: id (required), date, task, time, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 41 tools

    Disambiguation1/5

    Multiple tools overlap significantly: `everhour_get_current_timer` and `everhour_get_running_timer` both retrieve the running timer; `everhour_timer_status` provides similar info. Time entry operations are split confusingly between `create/update/delete_time_record` and `add/update/delete_task_time`. Also, `everhour_list_tasks` with project filter and `everhour_get_tasks_for_project` serve nearly the same purpose.

    Naming Consistency3/5

    All tools share the `everhour_` prefix and mostly follow a verb_noun pattern, but there are inconsistencies: `everhour_add_time_to_task` vs. `everhour_create_time_record` use different verbs for analogous actions; `everhour_timer_status` is not a clear verb_noun; `everhour_list_all_sections` vs. `everhour_get_section` mixes list/get patterns. Overall readable but not strictly uniform.

    Tool Count2/5

    With 41 tools, the server is well beyond the 15-tool sweet spot. While the domain covers multiple resources (projects, tasks, time, timers, clients, sections, users), the count feels bloated due to redundant timer endpoints and overlapping time entry methods. This makes the API surface harder to navigate.

    Completeness4/5

    The server covers full CRUD for projects, tasks, clients, sections, and time records, plus timer controls and user info. Minor gaps exist, such as no explicit task assignment to users or bulk operations, but core lifecycle coverage is solid and most workflows can be executed without workarounds.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers