Why an MCP server for MOCO at all?
The Model Context Protocol (MCP) has become the common denominator through which AI agents talk to business software. Once a system has an MCP server, Claude, ChatGPT Desktop and other clients can reach its functions without any extra work.
For many mid-sized and boutique service firms in the DACH region, MOCO occupies exactly the middle ground between a classic ERP and pure time tracking: projects, time logging, quotes, orders, invoices. Precisely the processes where we wanted AI assistance internally - and precisely the place where no official MCP connection existed.
What the server covers
- Projects - list, retrieve, archive, tasks, reports, contracts.
- Activities & time entries - full CRUD, timer control.
- Master data - users, companies, contacts, units.
- Accounting context - invoices, schedules, deals, quotes.
- Comments on individual entities.
How we run it internally
The server runs in our own working environment as a Claude Desktop integration. Typical tasks: pulling a weekly review out of the logged activities, checking the hours booked against a project, preparing invoice drafts. What used to mean several click paths through the MOCO interface is now a question and a confirmation.
What deliberately does not happen automatically: actually sending invoices or closing records. Write operations with hard external consequences still require confirmation - the same principle we apply in client projects.
Source code & usage
MIT licence, written entirely in TypeScript, with a test suite. See the README for installation and configuration.
