@everhour/mcp-server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@everhour/mcp-server start timer for task 'Design homepage'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@everhour/mcp-server
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-serverPrerequisites
Node.js 18+
Everhour account with paid plan (API access required)
Everhour API key (get it from Everhour Settings ā My Profile)
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 optionseverhour_get_project- Get details of a specific projecteverhour_create_project- Create a new projecteverhour_update_project- Update project detailseverhour_delete_project- Delete a project
Core Task Management:
everhour_list_tasks- List tasks with filtering by project, status, assigneeeverhour_get_task- Get details of a specific taskeverhour_create_task- Create a new taskeverhour_update_task- Update task detailseverhour_delete_task- Delete a task
Extended Task Features:
everhour_get_tasks_for_project- Get all tasks for specific projecteverhour_update_task_estimate- Update task estimateeverhour_delete_task_estimate- Delete task estimateeverhour_add_time_to_task- Add time directly to taskeverhour_update_task_time- Update task timeeverhour_delete_task_time- Delete time from task
everhour_list_time_records- List time records with date/project filteringeverhour_get_time_record- Get details of a specific time recordeverhour_create_time_record- Log time (supports human-readable formats)everhour_update_time_record- Update existing time recordseverhour_delete_time_record- Delete a time record
Core Timer Functions:
everhour_get_current_timer- Get the currently running timereverhour_start_timer- Start a new timereverhour_stop_timer- Stop the current timereverhour_list_timers- List timer historyeverhour_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 clientseverhour_get_client- Get details of a specific clienteverhour_create_client- Create a new clienteverhour_update_client- Update client detailseverhour_delete_client- Delete a client
everhour_list_all_sections- List all sections (global search)everhour_get_section- Get details of a specific sectioneverhour_create_section- Create a new sectioneverhour_update_section- Update section detailseverhour_delete_section- Delete a section
everhour_get_current_user- Get current user profileeverhour_list_team_users- List all team userseverhour_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 |
| ā Yes | - | Your Everhour API key |
| ā No |
| API base URL |
| ā No |
| 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-serverClaude 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=falseOr in full mode:
š EVERHOUR MCP SERVER - FULL MODE ACTIVE
All 37 tools available
To enable readonly mode: Set EVERHOUR_READONLY_MODE=trueš Documentation
API Coverage Report - Complete endpoint mapping
Examples Guide - Comprehensive usage examples
Official Everhour API - Official API 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 startProject 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 pointScripts
npm run dev- Development mode with auto-reloadnpm run build- Build TypeScript to JavaScriptnpm start- Start the built servernpm run lint- Run ESLintnpm run lint:fix- Fix ESLint issuesnpm run clean- Clean build directory
š¤ Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Fork the repository
Create your feature branch (
git checkout -b feature/amazing-feature)Commit your changes (
git commit -m 'Add some amazing feature')Push to the branch (
git push origin feature/amazing-feature)Open a Pull Request
š License
This project is licensed under the MIT License - see the LICENSE file for details.
š Links
š Support
Issues: GitHub Issues
Everhour API: Official Documentation
MCP Protocol: MCP Documentation
š 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 toolseverhour_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
Scored across 41 tools
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.
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.
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.
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
Related MCP Connectors
Connects AI assistants to TrackingTime for querying time entries, projects, tasks, customers, and team data using natural language.
Connect your AI assistant to Taskford to plan projects, manage resources, and track time.
Manage Avaza projects, tasks, timesheets, expenses, invoices, and scheduling from AI assistants.
Time tracking you talk to: log, check and fix your work hours from your AI assistant.
Related MCP Servers
- AlicenseAqualityDmaintenanceIntegrates with Harvest time tracking API, enabling AI assistants to manage time entries, projects, clients, and tasks through natural language commands.1137MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Clockify time tracking API to manage time entries, projects, tasks, and workspaces through natural language commands.33 npm5ISC
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to the TrackingTime API v4 for managing projects, tasks, and team assignments. Users can start or stop timers, log manual time entries, and organize project workflows using natural language.16 npmMIT

TrackingTime MCPofficial
AlicenseNot gradedqualityCmaintenanceConnects AI assistants to TrackingTime for querying time entries, projects, tasks, customers, and team data using natural language.16 npmMIT