MOCO and AI: Is there an MCP server for MOCO?

MOCO is, according to itself, ERP software for agencies, with projects, time tracking, billing and planning. If you want an AI assistant such as Claude or ChatGPT to work with this data, you ask: is there an MCP server for it?

In short

Yes. MOCO runs an official MCP server per account. It is an opt-in in the account settings, where you set whether the assistant may only read or also write. The chatbot must support MCP and OAuth. Sign-in uses the person’s own MOCO login. We found no delete tool in MOCO’s list. Two MOCO pages contradict each other on the data region.

What MOCO offers itself

The MCP server. According to MOCO, it runs at https://<subdomain>.mocoapp.com/mcp. MOCO describes it as an interface for chatbots that support MCP and OAuth. The page lists 68 tools, among others for leads, quotes, projects, time tracking, invoices, purchases, companies, contacts, planning and personnel. The blog presented the server on 4 February 2026. Tools were added on 26 May 2026 and 2 June 2026. MOCO writes that the scope grows step by step, based on user feedback. To use new tools you may have to renew the connection.

Sign-in and permissions. The connection uses the person’s own MOCO login. According to MOCO, the person has over MCP only the rights they have in the app. At account level you set whether read rights only or also write rights apply. MOCO recommends releasing read rights first and checking actions before they run.

Claude and ChatGPT. MOCO has a guide for Claude and one for ChatGPT. In Claude you add a custom connector with the MCP address under connectors. In ChatGPT you enable developer mode, create an app with the MCP address and choose OAuth, with client ID and secret left empty. MOCO writes: the connection may require a paid account and admin rights. According to the Claude Help Center, custom connectors are available on Free, Pro, Max, Ultra, Team and Enterprise. The Free plan allows one. On Team plans only Owners add connectors, on Enterprise plans only Owners and people with a suitable role. MOCO does not say which ChatGPT plans are needed. No MOCO source mentions an entry in the Claude or ChatGPT connector directory. We did not search the directories themselves.

Plan. The pricing page names the plans Core, Pro and Unlimited. MCP appears in no feature list. Of AI the page names only the AI-assisted OCR: an add-on in Pro, included in Unlimited. According to MOCO, the AI feature is free during the beta phase. The pricing page lists leads, purchases and capacity planning only from Pro. MOCO does not say whether the matching tools are missing on Core. We found no price for after the beta.

Deleting. The list holds tools to retrieve, create and update. We found no delete tool in it. The list can change. According to MOCO, the REST API can create and delete purchase drafts.

A REST API. The API uses a personal API key or up to three account keys. According to MOCO, API access can be switched off completely in the account settings. Since 20 May 2026 there is an OpenAPI specification, which MOCO explicitly names for AI agents too. According to MOCO it is a beta.

AI in the product. According to MOCO, all AI features are optional. They include time tracking and comments by voice input, a smart import for companies, contacts and leads, and since 16 September 2026 an overview of projects, clients, suppliers and people. The overview appears only if the person has the required access rights. There is also an AI-assisted text recognition for incoming invoices under Settings > Extensions > OCR. According to MOCO it costs EUR 0.20 per document read.

Data region. Here the sources contradict each other. The security and operations page says MOCO runs in Switzerland on servers of Netskin GmbH in the IWB data centre in Basel. The FADP/GDPR page names three providers for operating the MOCO Cloud: Hetzner (Germany, Finland), Exoscale (Germany, Austria, Switzerland) and Netskin with IWB (Switzerland). We found no rule for how an account is assigned to a region. According to the GDPR page, MOCO works only with European and Swiss companies to operate the service. Backups are with Amazon Web Services (EU), according to the list. For supplementary services MOCO uses subcontractors in the USA and the United Kingdom. For Switzerland, MOCO refers to the European Commission adequacy decision 2000/518/EC. The AI features are a special case: according to the GDPR page, OpenAI and Anthropic process the voice and text input in the USA, only with opt-in and without training on this data. The page lists them as subcontractors for “AI-supported functions”. MOCO does not say whether this covers the MCP server. What a chatbot reads from MOCO over MCP is processed by its provider under its own terms. According to the terms, the contracting party is everii Switzerland GmbH. A data processing agreement comes with it. According to the GDPR page, the company was called “hundertzehn” until 30 July 2026.

What the community and platforms offer

There are several community servers on GitHub. According to its README, niondigital/moco-mcp reads time entries, projects, holidays and presence. It is MIT-licensed, starts with npx and needs an API key and subdomain. The last commit is from 6 August 2025. fillidefilla/moco-mcp is also MIT-licensed and, according to its README, reads projects, invoices, time entries, people and absences. The last commit is from 14 July 2026. According to its README, codestra/moco-mcp offers 45 tools, including deleting time entries, comments and project assignments. The repository holds no licence file. The README and package.json name the licence ISC. Levisteria/moco-mcp-server generates its tools from the OpenAPI specification and, according to its README, also allows deleting unless you set the read-only mode. The package names the licence ISC. The README shows an MIT badge, and the repository holds no licence file.

Commercial platforms offer MOCO actions through their own MCP servers: Zapier, viaSocket, Composio and AnythingMCP. According to Zapier, each tool call uses two tasks of the plan. The pages do not prove which rights they use in MOCO. According to MOCO, customers should not use third-party MCP proxies, aggregators or relay servers, because content can be read through them and, with write rights enabled, data can be changed.

What this means for your company

• Release read rights first. MOCO recommends this itself. You set write rights at account level.
• The assistant acts with the rights of the signed-in person. Check roles and access rights in MOCO.
• Use the official address on mocoapp.com. MOCO warns against intermediary services.
• If data must stay in the EU, ask MOCO for the region of your account. The sources name Switzerland and the EU, but no assignment per account.
• According to MOCO, its AI features send input to OpenAI and Anthropic in the USA. What reaches your chatbot is subject to its terms.