- Home
- MCP servers
- MOCO
MOCO
- javascript
4
GitHub Stars
javascript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"niondigital-moco-mcp": {
"command": "npx",
"args": [
"-y",
"@niondigital/moco-mcp"
],
"env": {
"MOCO_API_KEY": "your-moco-api-key",
"MOCO_SUBDOMAIN": "your-subdomain"
}
}
}
}You run a MOCO MCP Server to securely expose employee data from MOCO for time tracking, project management, holidays, and presences to your MCP clients. It acts as a read‑only bridge, enabling your tools and prompts to fetch structured insights without modifying MOCO data.
How to use
Start by running the MCP server locally or in your environment, then connect your MCP client to the provided server configuration. You can use the quick start command to spin up the server, or integrate the server into your preferred MCP client by supplying the required environment variables (API key and subdomain). Once running, you can invoke the included tools and prompts to fetch activities, projects, holidays, presences, and more, and use the results to build reports, dashboards, or automated analyses.
How to install
Prerequisites: install Node.js version 18 or higher and obtain a MOCO API key with subdomain access.
- Install the MCP server locally using the standard quick start command.
npx -y @niondigital/moco-mcp
Configuration and usage notes
Choose how you run the server. The simplest method starts the MCP server via npx, while a fully local development path shows how to run from source with a node command.
# Local development start (built from source)
node /path/to/moco-mcp/dist/index.js
Additional setup different MCP clients use
Integrate the MCP server with your client by configuring an MCP server entry that references the runtime command and required environment variables. The following are examples from typical client configurations.
Security and environment variables
Store sensitive credentials as environment variables and do not hard‑code them in your configuration. The required variables are MOCO_API_KEY and MOCO_SUBDOMAIN.
Troubleshooting tips
If you encounter authentication errors, verify that your MOCO API key is correct, has the necessary permissions, and is set in the environment for your MCP client. If you see subdomain errors, ensure you use only the subdomain portion (not the full URL). For Node version issues, confirm you are running Node.js 18 or newer. If the MCP client cannot locate the tool, restart the client and recheck environment variables.
Advanced configuration
Local development from source shows how to run the server directly from the built distribution. If you prefer containerized deployments, you can use a Docker setup to install and run the MCP server.
Notes for persistent use
In production, prefer a stable runtime command and ensure MOCO API credentials are managed by your deployment platform’s secret management. Regularly rotate API keys and monitor access to the MCP server.
Examples of connecting from a client
The following configuration illustrates how to integrate the MCP server with a client, using a standard stdio runtime and the required environment variables.
Available tools
get_activities
Get activities within a date range, with optional project filtering and summation by date, project, and task.
get_user_projects
List all assigned projects or search by a query.
get_user_project_tasks
Fetch all tasks for a specific assigned project.
get_user_holidays
Get holiday overview for a year with calculations.
get_user_presences
Get presence data within a date range with daily summaries.
get_user_sick_days
Get sick day overview for a year with calculations.
get_public_holidays
Get public holidays for a year with working day calculations.