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

awork describes itself as project management software for agencies, with projects, tasks, time tracking and capacity planning. If you want an AI assistant such as Claude or ChatGPT to work with this data, the question is: is there an MCP server for it?

In short

Yes. awork runs an official, centrally hosted MCP server. Claude and ChatGPT sign in with OAuth using the awork account. According to awork, the assistant has only the rights of that account. According to the developer docs, it can also change and delete data. awork names no plan for the server. According to awork, central data storage is on Azure in Germany.

What awork offers itself

The MCP server. According to awork, it is at https://api.awork.com/api/v1/mcp. The developer docs describe it like this: it gives access to all functions of the awork API, such as projects, tasks, time entries, users, companies and files. It has no tool per endpoint. Instead it provides guidance for the language model, which generates the API code it needs. The server runs this code with the signed-in access. According to the docs, a call can retrieve data or create, update and delete it. The server applies the same rate limits as the API. In a community post of 3 June 2026 (German), awork writes that the server now supports the whole API, needs fewer tokens in context and gives access to Docs and best practices. We found no beta label in the awork sources we read.

Development status. The help article shows the status of 19 October 2026. On 14 August 2026 a forum user reported that ChatGPT failed with a protocol error. According to awork, the cause was a differing MCP version that the new server rejected. awork was working on a fix. On 19 August the user wrote that the connection worked again. The same user reports problems uploading and downloading files through ChatGPT in another post. awork asked for details on 21 September 2026. We found no answer to that. This is a single report.

Sign-in and rights. According to the developer docs, the server supports OAuth 2.1 and dynamic client registration. The client then registers itself, and you do not create a client application in awork. The OAuth metadata lists the scope full_access. We found no read-only scope there. So there is no switch to allow reading only. Check the rights of the person whose account the assistant uses. The server also accepts an API key. According to awork, it is permanently valid, not bound to a person and grants admin permissions. According to the help article, only admins create it.

Claude and ChatGPT. According to awork, in Claude you create a custom connector with the MCP address under Connectors. In ChatGPT you search for awork under Apps and connect it. awork also names Codex, Claude Code and Visual Studio Code. According to the Claude Help Center, custom connectors are available on Free, Pro, Max, Ultra, Team and Enterprise. The Free plan allows one. In Team plans only Owners add connectors, in Enterprise plans only Owners and roles with access to manage libraries. awork does not name the ChatGPT plans you need. The awork integrations overview lists ChatGPT with the label “Basic”. We found no explanation of that label and do not know whether it refers to the MCP server. For Microsoft Copilot, awork names “awork agents for Microsoft 365 Copilot and Teams” in the Microsoft Marketplace. That listing does not say whether it uses the MCP server.

Plan. The help article on the MCP server and the pricing page name no plan for the server. The help article sits in the awork AI section. According to awork, awork AI is a separate subscription on top of the regular awork subscription. awork does not say whether you need it for the MCP server.

A REST API. The API is publicly documented, and the OpenAPI specification is at api.awork.com/openapi/v1. awork writes in the introduction that what you see in awork you can usually do through the API. awork also publishes a command-line tool on GitHub (MIT licence, last commit 18 September 2026).

AI in the product. According to awork, awork AI consists of a chat and custom agents and is a separate subscription. The product page calls chat and Docs live and agents still on a waitlist, while the help centre already describes them. It costs per user and month EUR 15 (AI Starter), 30 (Plus), 60 (Pro), 120 (Max) or 450 (Ultra), with a rising credit allowance. According to awork, once the subscription is active, all active users of a workspace need at least AI Starter. According to awork, the regular plans from Standard include a limited credit allowance at no extra cost. The Basic plan no longer includes credits and therefore no AI chat. There is a 14-day trial. According to awork, awork uses Microsoft Azure AI Foundry, Google Vertex AI, Amazon Bedrock or TensorX, depending on the model. Admins can switch off AI features and models. awork writes that the data is not used to train general AI models. According to awork, agents can also use their own MCP connectors. That is the opposite direction: awork then calls third-party services. According to awork, the terms, data protection rules and processing locations of third-party MCP servers apply to those.

Data location. According to awork, central data storage is on Microsoft Azure in Germany, in a dedicated Azure tenant of awork. For optional features such as some AI models, awork uses further sub-processors. Depending on the service, they process only in Germany, in the EU or the EEA, or in limited cases in third countries. According to awork, the binding list is in the data processing agreement, which we did not read. According to the imprint, the provider is awork GmbH in Hamburg.

What the community and platforms offer

We found one npm package: awork-mcp. It uses the Apache-2.0 licence and, according to its README, is generated from the awork API with Stainless. It runs with npx and an API key. As maintainer, npm lists an address of Brand Boosting GmbH. The author field names “Awork” with an awork address, and the description speaks of an “official MCP server”. We found no confirmation from awork. There is a single version from 9 June 2025. The GitHub repository Brand-Boosting-GmbH/awork-typescript named in the package returns 404. We read the package code: it uses api.awork.com and the API key. We did not run it. On GitHub we found no other server that connects awork through MCP.

Commercial platforms offer awork actions through their own MCP servers: Zapier, viaSocket and Pipedream. viaSocket lists 62 actions. The pages do not show which rights they use in awork.

What this means for your company

• The official server can change and delete data. We found no read-only mode. Check which rights the connected account has.
• The assistant acts with the rights of the signed-in person. An API key grants admin permissions instead. Use it only if the client cannot do OAuth.
• According to awork, central storage is in Germany. What reaches the AI assistant falls under its terms.
• Ask awork whether the MCP server needs a specific plan or the AI subscription. The sources do not say.
• A user reports that uploading and downloading files through the server is unreliable. Test this before you rely on it.