by niondigital
MOCO integrates with project management software for seamless project tracking, vacation planning, and productivity insi
Integrates with MOCO's time tracking and project management platform to provide conversational access to activities, projects, holidays, presences, and sick days data with vacation planning assistance, productivity insights, and work-life balance analysis.
MOCO is a community-built MCP server published by niondigital that provides AI assistants with tools and capabilities via the Model Context Protocol. MOCO integrates with project management software for seamless project tracking, vacation planning, and productivity insi It is categorized under analytics data, productivity.
You can install MOCO in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
MOCO is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Useful MCP listing: MOCO is the kind of server we cite when onboarding engineers to host + tool permissions.
We evaluated MOCO against two servers with overlapping tools; this profile had the clearer scope statement.
MOCO is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Strong directory entry: MOCO surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We evaluated MOCO against two servers with overlapping tools; this profile had the clearer scope statement.
We wired MOCO into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Useful MCP listing: MOCO is the kind of server we cite when onboarding engineers to host + tool permissions.
MOCO has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
MOCO is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
I recommend MOCO for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
showing 1-10 of 26
A Model Context Protocol (MCP) server that provides employee read access to the MOCO API for time tracking, project management, holiday tracking, and presence monitoring.
npx -y @niondigital/moco-mcp
That's it! The server will start and be ready to connect to your MCP client.
Add to your Claude Desktop claude_desktop_config.json file:
MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"moco": {
"command": "npx",
"args": ["-y", "@niondigital/moco-mcp"],
"env": {
"MOCO_API_KEY": "your-moco-api-key",
"MOCO_SUBDOMAIN": "your-subdomain"
}
}
}
}
Add to your Cursor settings:
MacOS: ~/Library/Application Support/Cursor/User/settings.json
Windows: %APPDATA%\Cursor\User\settings.json
Linux: ~/.config/Cursor/User/settings.json
{
"mcpServers": {
"moco": {
"command": "npx",
"args": ["-y", "@niondigital/moco-mcp"],
"env": {
"MOCO_API_KEY": "your-moco-api-key",
"MOCO_SUBDOMAIN": "your-subdomain"
}
}
}
}
Add to your Windsurf MCP configuration:
{
"mcpServers": {
"moco": {
"command": "npx",
"args": ["-y", "@niondigital/moco-mcp"],
"env": {
"MOCO_API_KEY": "your-moco-api-key",
"MOCO_SUBDOMAIN": "your-subdomain"
}
}
}
}
Add the MCP server to Claude Code:
claude mcp add -e MOCO_API_KEY="your-moco-api-key" -e MOCO_SUBDOMAIN="your-subdomain" moco -- npx -y @niondigital/moco-mcp
Configure Gemini CLI with MCP support:
{
"mcpServers": {
"moco": {
"command": "npx",
"args": ["-y", "@niondigital/moco-mcp"],
"env": {
"MOCO_API_KEY": "your-moco-api-key",
"MOCO_SUBDOMAIN": "your-subdomain"
}
}
}
}
Kiro > MCP Servers+ Add{
"mcpServers": {
"moco": {
"command": "npx",
"args": [
"-y",
"@niondigital/moco-mcp"
],
"env": {
"MOCO_API_KEY": "your-moco-api-key",
"MOCO_SUBDOMAIN": "your-subdomain"
},
"disabled": false,
"autoApprove": []
}
}
}
Save to apply changesProgram (right side) > Install > Edit mcp.json{
"mcpServers": {
"moco": {
"command": "npx",
"args": ["-y", "@niondigital/moco-mcp"],
"env": {
"MOCO_API_KEY": "your-moco-api-key",
"MOCO_SUBDOMAIN": "your-subdomain"
}
}
}
}
Save to apply changesProgram) or by clicking the plug icon at the bottom of the chat boxhttps://niondigital.mocoapp.com/profile/integrationshttps://yourcompany.mocoapp.comyourcompanyYou can set environment variables in several ways:
Option 1: System Environment Variables
export MOCO_API_KEY="your-moco-api-key"
export MOCO_SUBDOMAIN="your-subdomain"
Option 2: .env File (for local development)
MOCO_API_KEY=your-moco-api-key
MOCO_SUBDOMAIN=your-subdomain
Option 3: MCP Client Configuration (recommended)
Use the env section in your MCP client configuration as shown above.
| Tool | Description | Parameters |
|---|---|---|
get_activities | Get activities within a date range with summation and optional project filtering | startDate, endDate (ISO 8601), projectId (optional) |
get_user_projects | List all assigned projects or search by query | query (optional) |
get_user_project_tasks | Get all tasks for a specific assigned project | projectId |
get_user_holidays | Get holiday overview for a year with calculations | year |
get_user_presences | Get presence data within a date range with daily summaries | startDate, endDate (ISO 8601) |
get_user_sick_days | Get sick days overview for a year with calculations | year |
get_public_holidays | Get public holidays for a year with working days calculations | year |
The MoCo MCP server provides 8 intelligent prompts that orchestrate multiple tools to deliver comprehensive insights:
| Prompt | Description | Key Parameters |
|---|---|---|
weekly_time_report | Generates detailed weekly time tracking report with project breakdown | week_start, include_billable_analysis |
vacation_planning_assistant | Assists with vacation planning by analyzing available days and holidays | planned_start_date, planned_end_date |
personal_productivity_insights | Analyzes work habits and provides productivity recommendations | analysis_period, focus_area |
monthly_business_review | Creates comprehensive business reports with trends and metrics | month, year, include_comparisons |
smart_work_life_balance_advisor | Evaluates work-life balance with personalized recommendations | analysis_weeks, target_hours_per_week |
project_time_analysis | Detailed project time analysis with efficiency metrics | project_ids, time_period |
team_capacity_overview | Team capacity planning with absence and resource analysis | planning_horizon, include_holidays |
work_hours_compliance_check | Compliance check for working time regulations | check_period, max_weekly_hours, max_daily_hours |
Weekly Time Report:
{
"name": "weekly_time_report",
"arguments": {
"week_start": "2024-01-15",
"include_billable_analysis": true
}
}
Vacation Planning:
{
"name": "vacation_planning_assistant",
"arguments": {
"planned_start_date": "2024-07-15",
"planned_end_date": "2024-07-29"
}
}
Work-Life Balance Analysis:
{
"name": "smart_work_life_balance_advisor",
"arguments": {
"analysis_weeks": 6,
"target_hours_per_week": 40
}
}
Compliance Check:
{
"name": "work_hours_compliance_check",
"arguments": {
"check_period": "last_month",
"max_weekly_hours": 48,
"max_daily_hours": 10
}
}
Filter all activities in a date range:
{
"name": "get_activities",
"arguments": {
"startDate": "2024-01-01",
"endDate": "2024-01-31"
}
}
Filter activities for a specific project:
{
"name": "get_activities",
"arguments": {
"startDate": "2024-01-01",
"endDate": "2024-01-31",
"projectId": 123456
}
}
Sample Output:
Activities from 2024-01-01 to 2024-01-31:
2024-01-15:
Project 123 (Website Redesign):
Task 456 (Frontend Development): 4.5h (4:30)
Task 789 (Backend API): 3.25h (3:15)
Project total: 7.75h (7:45)
Daily total: 7.75h (7:45)
Grand total: 7.75h (7:45)
List all assigned projects:
{
"name": "get_user_projects",
"arguments": {}
}
Search projects:
{
"name": "get_user_projects",
"arguments": {
"query": "website"
}
}
{
"name": "get_user_project_tasks",
"arguments": {
"projectId": 123456
}
}
{
"name": "get_user_holidays",
"arguments": {
"year": 2024
}
}
Sample Output:
Holiday overview for 2024:
Taken holiday days:
- 2024-03-15: 1.0 day
- 2024-04-22: 0.5 day
- 2024-07-08: 1.0 day
Summary:
- Taken vacation: 2.5 days
- Annual entitlement: 25 days
- Utilization: 10% (2.5/25)
- Remaining vacation: 22.5 days
{
"name": "get_user_presences",
"arguments": {
"startDate": "2024-01-01",
"endDate": "2024-01-07"
}
}
Sample Output:
Presences from 2024-01-01 to 2024-01-07:
Daily presences:
- 2024-01-01: 8.25h (8:15)
- 2024-01-02: 7.5h (7:30)
- 2024-01-03: 8.0h (8:00)
Grand total: 23.75h (23:45)
Statistics:
- Working days: 3
- Average per day: 7.92h (7:55)
{
"name": "get_user_sick_days",
"arguments": {
"year": 2024
}
}
{
"name": "get_public_holidays",
"arguments": {
"year": 2024
}
}
Sample Output:
Public holidays for 2024:
Holiday dates:
- 2024-01-01: New Year's Day
- 2024-04-01: Good Friday
- 2024-04-03: Easter Monday
- 2024-05-01: Labor Day
- 2024-05-09: Ascension Day
- 2024-05-20: Whit Monday
- 2024-10-03: German Unity Day
- 2024-12-25: Christmas Day
- 2024-12-26: Boxing Day
Summary:
- Total public holidays: 9 days
- Approximate working days: 251 days
If you want to run from source:
git clone https://github.com/niondigital/moco-mcp.git
cd moco-mcp
npm inst
---
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.