analytics-dataproductivity

MOCO

niondigital

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.

github stars

5

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

best for

  • / General purpose MCP workflows

capabilities

    what it does

    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.

    about

    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.

    how to install

    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.

    license

    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.

    readme

    📊 MOCO MCP Server

    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.

    ⚡ Quick Start

    npx -y @niondigital/moco-mcp
    

    That's it! The server will start and be ready to connect to your MCP client.

    🚀 Installation

    Prerequisites

    • Node.js ≥ 18.0.0
    • MOCO account with API access
    • MOCO API key and subdomain

    MCP Client Integration

    <details> <summary><strong>Claude Desktop</strong></summary>

    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"
          }
        }
      }
    }
    
    </details> <details> <summary><strong>Cursor</strong></summary>

    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"
          }
        }
      }
    }
    
    </details> <details> <summary><strong>Windsurf</strong></summary>

    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"
             }
          }
       }
    }
    
    </details> <details> <summary><strong>Claude Code (CLI)</strong></summary>

    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
    
    </details> <details> <summary><strong>Gemini CLI</strong></summary>

    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"
             }
          }
       }
    }
    
    </details> <details> <summary><strong>Kiro</strong></summary>
    1. Go to Kiro > MCP Servers
    2. Add new MCP server by clicking + Add
    3. Paste the configuration below:
    {
      "mcpServers": {
        "moco": {
        "command": "npx",
        "args": [
          "-y",
          "@niondigital/moco-mcp"
        ],
        "env": {
           "MOCO_API_KEY": "your-moco-api-key",
           "MOCO_SUBDOMAIN": "your-subdomain"
        },
        "disabled": false,
        "autoApprove": []
        }
      }
    }
    
    
    1. Click Save to apply changes
    </details> <details> <summary><strong>LM Studio</strong></summary>
    1. Go to Program (right side) > Install > Edit mcp.json
    2. Paste the configuration below:
    {
      "mcpServers": {
        "moco": {
          "command": "npx",
          "args": ["-y", "@niondigital/moco-mcp"],
           "env": {
              "MOCO_API_KEY": "your-moco-api-key",
              "MOCO_SUBDOMAIN": "your-subdomain"
           }
        }
      }
    }
    
    1. Click Save to apply changes
    2. Toggle MCP server on/off from the right hand side (under Program) or by clicking the plug icon at the bottom of the chat box
    </details>

    🔑 MOCO API Setup

    Getting Your API Credentials

    1. Log into your MOCO account
    2. Navigate to API settings:
      • Go to ProfileIntegrations
      • Or visit: https://niondigital.mocoapp.com/profile/integrations
    3. Copy the listed API key
    4. Note your subdomain:
      • From your MOCO URL: https://yourcompany.mocoapp.com
      • Your subdomain is: yourcompany

    Environment Variables

    You 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.

    🛠️ Available Tools

    ToolDescriptionParameters
    get_activitiesGet activities within a date range with summation and optional project filteringstartDate, endDate (ISO 8601), projectId (optional)
    get_user_projectsList all assigned projects or search by queryquery (optional)
    get_user_project_tasksGet all tasks for a specific assigned projectprojectId
    get_user_holidaysGet holiday overview for a year with calculationsyear
    get_user_presencesGet presence data within a date range with daily summariesstartDate, endDate (ISO 8601)
    get_user_sick_daysGet sick days overview for a year with calculationsyear
    get_public_holidaysGet public holidays for a year with working days calculationsyear

    🎯 Available Prompts

    The MoCo MCP server provides 8 intelligent prompts that orchestrate multiple tools to deliver comprehensive insights:

    PromptDescriptionKey Parameters
    weekly_time_reportGenerates detailed weekly time tracking report with project breakdownweek_start, include_billable_analysis
    vacation_planning_assistantAssists with vacation planning by analyzing available days and holidaysplanned_start_date, planned_end_date
    personal_productivity_insightsAnalyzes work habits and provides productivity recommendationsanalysis_period, focus_area
    monthly_business_reviewCreates comprehensive business reports with trends and metricsmonth, year, include_comparisons
    smart_work_life_balance_advisorEvaluates work-life balance with personalized recommendationsanalysis_weeks, target_hours_per_week
    project_time_analysisDetailed project time analysis with efficiency metricsproject_ids, time_period
    team_capacity_overviewTeam capacity planning with absence and resource analysisplanning_horizon, include_holidays
    work_hours_compliance_checkCompliance check for working time regulationscheck_period, max_weekly_hours, max_daily_hours

    Prompt Examples

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

    📝 Tool Examples

    Get Activities

    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)
    

    Get User Projects

    List all assigned projects:

    {
      "name": "get_user_projects",
      "arguments": {}
    }
    

    Search projects:

    {
      "name": "get_user_projects",
      "arguments": {
        "query": "website"
      }
    }
    

    Get User Project Tasks

    {
      "name": "get_user_project_tasks",
      "arguments": {
        "projectId": 123456
      }
    }
    

    Get User Holidays

    {
      "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
    

    Get User Presences

    {
      "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)
    

    Get User Sick Days

    {
      "name": "get_user_sick_days",
      "arguments": {
        "year": 2024
      }
    }
    

    Get Public Holidays

    {
      "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
    

    🔧 Advanced Configuration

    <details> <summary><strong>Local Development</strong></summary>

    If you want to run from source:

    git clone https://github.com/niondigital/moco-mcp.git
    cd moco-mcp
    npm inst
    
    ---
    

    FAQ

    What is the MOCO MCP server?
    MOCO is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
    How do MCP servers relate to agent skills?
    Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
    How are reviews shown for MOCO?
    This profile displays 26 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.6 out of 5—verify behavior in your own environment before production use.

    Use Cases

    Extended AI Capabilities

    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

    Context Enhancement

    Provide Claude with access to relevant context and data

    Example

    Load project documentation, access knowledge bases, query databases

    Get more accurate, context-aware responses

    Workflow Automation

    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

    Implementation Guide

    Prerequisites

    • Claude Desktop 0.7.0+ or Cursor IDE with MCP support
    • Basic understanding of MCP architecture and capabilities
    • Access credentials for integrated services (if required)
    • Willingness to experiment and iterate on configuration

    Time Estimate

    15-60 minutes depending on server complexity

    Installation Steps

    1. 1.Install MCP server: npm install -g [package-name] or via GitHub
    2. 2.Add server configuration to ~/.claude/mcp.json
    3. 3.Provide required credentials and configuration
    4. 4.Restart Claude Desktop to load new server
    5. 5.Test basic functionality with simple prompts
    6. 6.Explore capabilities and experiment with use cases
    7. 7.Document successful patterns for reuse

    Troubleshooting

    • MCP server not loading: Check config syntax, verify installation
    • Connection errors: Check network, firewall, credentials
    • Feature not working: Read server docs, check required parameters
    • Performance issues: Monitor resource usage, check for network latency
    • Conflicts with other servers: Check port assignments, namespace collisions

    Best Practices

    ✓ Do

    • +Read server documentation thoroughly before setup
    • +Start with simple use cases to validate functionality
    • +Test in non-production environment first
    • +Monitor resource usage and performance
    • +Keep servers updated for bug fixes and new features
    • +Document configuration for team members
    • +Use environment variables for sensitive configuration

    ✗ Don't

    • Don't grant overly permissive access to MCP servers
    • Don't skip reading security considerations in docs
    • Don't expose sensitive data without proper controls
    • Don't run untrusted MCP servers without code review
    • Don't ignore error messages—investigate root cause

    💡 Pro Tips

    • Combine multiple MCP servers for powerful workflows
    • Create custom MCP servers for your specific needs
    • Share successful configurations with team
    • Use MCP inspector for debugging
    • Join MCP community for tips and troubleshooting

    Technical Details

    Architecture

    Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.

    Protocols

    • Model Context Protocol (MCP)
    • JSON-RPC 2.0
    • stdio or HTTP transport

    Compatibility

    • Claude Desktop
    • Cursor IDE
    • Custom MCP clients

    When to Use This

    ✓ 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.

    Integration

    • Tool composition: Chain multiple MCP tools in workflows
    • Context augmentation: Provide AI with relevant external data
    • Action delegation: Let AI execute tasks on external systems
    • Bidirectional sync: Keep AI context and external systems in sync

    Discussion

    Product Hunt–style comments (not star reviews)
    • No comments yet — start the thread.

    List & Promote Your MCP Server

    Share your MCP server with the developer community

    GET_STARTED →
    MCP server reviews

    Ratings

    4.626 reviews
    • Chinedu Khanna· Dec 24, 2024

      Useful MCP listing: MOCO is the kind of server we cite when onboarding engineers to host + tool permissions.

    • Amelia Menon· Dec 20, 2024

      We evaluated MOCO against two servers with overlapping tools; this profile had the clearer scope statement.

    • Shikha Mishra· Dec 4, 2024

      MOCO is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

    • Yash Thakker· Nov 23, 2024

      Strong directory entry: MOCO surfaces stars and publisher context so we could sanity-check maintenance before adopting.

    • Sakshi Patil· Nov 3, 2024

      We evaluated MOCO against two servers with overlapping tools; this profile had the clearer scope statement.

    • Chaitanya Patil· Oct 22, 2024

      We wired MOCO into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

    • Dhruvi Jain· Oct 14, 2024

      Useful MCP listing: MOCO is the kind of server we cite when onboarding engineers to host + tool permissions.

    • Tariq Ndlovu· Sep 13, 2024

      MOCO has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

    • Tariq Nasser· Aug 4, 2024

      MOCO is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

    • Ishan Reddy· Jul 23, 2024

      I recommend MOCO for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

    showing 1-10 of 26

    1 / 3