Daily 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., "@Daily MCP Server show my time summary for last week"
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.
Daily MCP Server
An MCP (Model Context Protocol) server that provides integration with the Daily Time Tracking API. This server allows you to interact with your Daily time tracking data through MCP-compatible clients like Claude Desktop.
Features
Get User Info: Retrieve information about your Daily account
List Activities: Get all your activities (with optional archived filtering)
Time Summary: Get time spent on activities within a date range
Timesheet Data: Get detailed daily timesheet information
Add Activities: Create new activities in Daily
Related MCP server: Timesheet MCP Server
Prerequisites
Daily Time Tracking App: You need to have Daily installed and configured
API Key: Enable the Web API in Daily preferences and get your API key
Node.js: Version 18 or higher
Setup
Install dependencies:
npm installBuild the project:
npm run buildSet your API key:
export DAILY_API_KEY="your-api-key-here"
Usage
Running the Server
npm startDevelopment Mode
npm run devAvailable Tools
get_user_info
Get information about your Daily user account.
get_activities
Get a list of all your activities.
includeArchivedActivities(boolean, optional): Whether to include archived activities (default: true)
get_summary
Get a summary of time spent on activities within a date range.
start(string, required): Start date in ISO 8601 format (e.g., "2025-01-01")end(string, required): End date in ISO 8601 format (e.g., "2025-01-31")includeArchivedActivities(boolean, optional): Whether to include archived activities (default: true)
get_timesheet
Get detailed timesheet data for a date range.
start(string, required): Start date in ISO 8601 formatend(string, required): End date in ISO 8601 formatincludeArchivedActivities(boolean, optional): Whether to include archived activities (default: true)
add_activities
Add new activities to Daily.
activities(array, required): Array of activities to addname(string, required): Name of the activitygroup(string, optional): Group name
archiveExistingActivities(boolean, optional): Whether to archive existing activities (default: false)
Integration with Claude Desktop
To use this server with Claude Desktop, add the following to your Claude Desktop configuration:
{
"mcpServers": {
"daily": {
"command": "node",
"args": ["/path/to/daily-mcp/dist/index.js"],
"env": {
"DAILY_API_KEY": "your-api-key-here"
}
}
}
}API Documentation
For detailed information about the Daily Time Tracking API, refer to the Daily App API Documentation or check the API documentation within the Daily app itself (Preferences > Integrations tab).
Development
Building
npm run buildDevelopment Mode
npm run devLicense
MIT
Available Tools
5 toolsadd_activitiesC
Add new activities to Daily
Inputs: activities (required), archiveExistingActivities.
get_activitiesB
Get list of activities from Daily
Inputs: includeArchivedActivities.
get_summaryC
Get time summary for activities within a date range
Inputs: end (required), start (required), includeArchivedActivities.
get_timesheetC
Get detailed timesheet data for a date range
Inputs: end (required), start (required), includeArchivedActivities.
get_user_infoA
Get information about the Daily user account
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Tools are mostly distinct: get_user_info and add_activities are clear, while get_activities, get_summary, and get_timesheet overlap in domain but differ in output (list vs. summary vs. detailed timesheet). Descriptions effectively clarify these boundaries, so confusion is minimal.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_activities, add_activities, get_timesheet). The verbs are limited to 'get' and 'add', which is intuitive for read/write operations, and there are no mixed conventions.
With 5 tools, the server is well-scoped for a time-tracking domain. Each tool covers a core need (user info, activities, summary, timesheet, adding activities) without superfluous or redundant endpoints.
The server provides good read coverage (user info, activities, summary, timesheet) and the ability to add activities, but lacks update and delete operations for activities. This is a notable gap for full lifecycle management, as users cannot correct or remove erroneous entries.
Maintenance
Related MCP Connectors
Read tracked time and projects; create projects and start or stop timers in DeskTime.
Read time entries, projects, clients, tasks and invoices; log and update tracked time.
Track time, manage clients and projects, review timesheets, and create invoices with OAuth.
Read jobs, timesheets and reports; log time, update entries and submit timesheets in ClickTime.
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides comprehensive integration with the Clockify time tracking API, enabling automated time entry management, project organization, task tracking, and reporting through a standardized interface.297 npm6MIT
- AlicenseNot gradedqualityDmaintenanceEnables automated timesheet management including creating entries, listing work activities, managing daily scrum updates, and viewing assigned projects with automatic authentication handling.8 npmMIT
- FlicenseAqualityCmaintenanceProvides access to RescueTime productivity data including daily summaries, activity tracking, productivity trends, category breakdowns, and hourly analysis to help understand and optimize time usage patterns.54-
- AlicenseNot gradedqualityDmaintenanceIntegrates with Clockify time tracking API to retrieve user information, manage projects, and log time entries with flexible time specifications across workspaces.MIT