# ChatGPT integration fails with MCP protocol version / clientCapabilities error **URL:** \ **Category:** Developer Forum\ **Created:** [14. August 2026 um 08:00 UTC](https://community.awork.com/t/chatgpt-integration-fails-with-mcp-protocol-version-clientcapabilities-error/4793 "2026-08-14T08:00:16Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Kjetil\_Ringen](https://avatars.discourse-cdn.com/v4/letter/k/f9ae1b/32.png) [@Kjetil\_Ringen](https://community.awork.com/u/Kjetil_Ringen)\ **Post date:** [14. August 2026 um 08:00 UTC](https://community.awork.com/t/chatgpt-integration-fails-with-mcp-protocol-version-clientcapabilities-error/4793/1 "2026-08-14T08:00:16Z")
Hello! I’m currently unable to use the awork MCP integration from ChatGPT. The connection had been working normally for approximately one month before this issue started yesterday, August 13, 2026. Since then, the connection has consistently failed before any actual awork API request is executed. The exact error returned is: `The reserved per-request metadata key '_meta/io.modelcontextprotocol/clientCapabilities' is not valid with protocol version '2025-11-25'.` The error is reproducible even with a minimal MCP call and is therefore not tied to a specific awork endpoint or resource such as tasks or time entries. I have tested the following: - Disconnecting and reconnecting the awork integration in ChatGPT - Re-authenticating the connection - Testing from a completely new ChatGPT conversation The same error occurs in all cases. The connection uses the standard awork MCP endpoint: `https://api.awork.com/api/v1/mcp` awork Support informed me that the current implementation uses ModelContextProtocol 2.1.0. The error indicates that the request contains the per-request metadata key `io.modelcontextprotocol/clientCapabilities`, while the connection is being handled as MCP protocol version `2025-11-25`. Update: connecting with Codex does not seem to return any issues. ---
**Author:** ![Sebastian](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/sebastian/32/1305_2.png) [@Sebastian](https://community.awork.com/u/Sebastian)\ **Post date:** [16. August 2026 um 19:45 UTC](https://community.awork.com/t/chatgpt-integration-fails-with-mcp-protocol-version-clientcapabilities-error/4793/2 "2026-08-16T19:45:40Z")
Hi @Kjetil_Ringen thanks for bringing this up. Apparently ChatGPT seems to send a mismatch of MCP version information which the latest version of our server rejects. We’re working on a fix to remain compatible, which should be available soon. ---
**Author:** ![Kjetil\_Ringen](https://avatars.discourse-cdn.com/v4/letter/k/f9ae1b/32.png) [@Kjetil\_Ringen](https://community.awork.com/u/Kjetil_Ringen)\ **Post date:** [19. August 2026 um 07:44 UTC](https://community.awork.com/t/chatgpt-integration-fails-with-mcp-protocol-version-clientcapabilities-error/4793/3 "2026-08-19T07:44:45Z")
I have deactivated and reconnected to the MCP today. It seems that everything is in order 😊