MOCO

MOCO connects agencies to projects, time entries, companies, invoices, and utilization reports through its REST API. This adapter reads those records and can book time for the API key's user.

Getting credentials

1. In your MOCO account, open Profile → Integrations and copy your personal API key into MOCO_API_KEY. A personal key follows your user's permissions. An account API key can instead be created under Settings → Extensions → API & Webhooks with read-only or full access; a read-only key cannot book time.
2. Set MOCO_SUBDOMAIN to the first part of your account URL only: for agency.mocoapp.com, use agency (no scheme or domain suffix). The adapter sends requests to https://agency.mocoapp.com/api/v1.

Permissions and privacy: list tools return only records visible to the key's user. A missing project or invoice may be a permission issue. Do not share a full-access key with people who should only read data. The connector stores the key as a credential.

Finding IDs: list companies and projects first. moco_get_project returns one project and its task IDs; use its numeric project and task IDs when booking time. For example, project 123456 and task 234567 are IDs, not names. A new activity belongs to the key's user.

Dates and duration: use YYYY-MM-DD dates, such as 2026-10-06. Activity list requests require both from and to so the result is bounded. moco_create_activity accepts duration in whole seconds; 2 hours is 7200 seconds. Each call creates a new entry, so do not retry a successful call or you may book duplicate time.

Pagination and limits: list tools accept a 1-based page. Up to 100 entries come back per page. Each list response carries _pagination next to the body while there are more pages: call again with page = _pagination.nextCursor and repeat until _pagination is absent, which means that was the last page. _headers["x-total"] is the total number of entries. Standard plans allow about 120 requests per two minutes; a 429 means wait before retrying.

Cloud reachability: *.mocoapp.com is publicly reachable over HTTPS. This adapter uses MOCO's REST API and does not require MOCO's optional MCP endpoint. PDF downloads, webhooks, invoice creation, and destructive operations are outside this adapter's scope.