Skip to content

ChatGPT OAuth succeeds, but MCP discovery fails after server/discover using protocol 2026-07-28 #170

Closed

Description

@KitKat31337

Before submitting

  • I've searched existing issues and this isn't a duplicate.
  • This is a reproducible bug in Calnode — not a configuration/setup question or a feature request.

What's the bug?

Connecting a self-hosted CalNode instance to ChatGPT completes OAuth successfully, but action discovery fails with:

{
  "error_code": "MCP_ACTION_DISCOVERY_FAILED",
  "message": "Authentication succeeded, action discovery failed",
  "cause": {
    "detail": "MCP server/discover response was inconsistent from example.com"
  }
}

Environment

  • Self-hosted CalNode using Docker Compose and the edge image tag.
  • CalNode reports its server version as edge; the exact running image digest/commit has not been captured.
  • Caddy terminates HTTPS and proxies to CalNode over HTTP.
  • Instance URL replaced with https://bookings.example.com throughout this report.

Observed behavior

Caddy access logs confirm that ChatGPT sends an authenticated request with:

User-Agent: openai-mcp/1.0.0
Mcp-Protocol-Version: 2026-07-28
Mcp-Method: server/discover
Content-Type: application/json
Accept: application/json, text/event-stream

CalNode returns HTTP 200 with Content-Type: text/event-stream. ChatGPT then reports the discovery error. No subsequent /mcp requests appear in the captured attempt, including no observable fallback to initialize or attempt to call tools/list.

A separate API-key-authenticated curl request declaring 2026-07-28 returns:

{
  "jsonrpc": "2.0",
  "id": "discovery-diagnostic",
  "result": {
    "resultType": "complete",
    "_meta": {
      "io.modelcontextprotocol/serverInfo": {
        "name": "calnode",
        "title": "Calnode booking",
        "version": "edge"
      }
    },
    "ttlMs": 0,
    "cacheScope": "public",
    "supportedVersions": [
      "2025-11-25",
      "2025-06-18",
      "2025-03-26",
      "2024-11-05"
    ],
    "capabilities": {
      "logging": {},
      "tools": {
        "listChanged": true
      }
    }
  }
}

The response is marked complete, but its supported-version list excludes the requested 2026-07-28 version.

Successful comparison

MCP Inspector works against the same endpoint:

  • Initializes using 2025-11-25.
  • Discovers all ten tools.
  • Successfully executes list_event_types with {}, returning the configured public event types.

Expected behavior

ChatGPT should complete discovery using a mutually supported protocol. If the requested version cannot be served, version negotiation should produce a response the client can handle, including legacy fallback where supported.

Investigation notes

One possibility is that ChatGPT’s current connector discovery flow requires 2026-07-28 and does not accept or fall back to CalNode’s advertised older versions. The captured attempt shows ChatGPT requesting 2026-07-28 and stopping after discovery, with no observable legacy handshake.

This is a hypothesis, not a confirmed ChatGPT requirement. The available evidence does not establish whether ChatGPT intentionally excludes older versions, has a fallback bug, or rejects some other aspect of the discovery response.

This points toward a discovery/version-negotiation compatibility issue, but responsibility has not been established between CalNode, the Go MCP SDK, and ChatGPT.

The exact response body sent to ChatGPT was not captured. The curl test uses an API key rather than ChatGPT’s OAuth token, so it is a comparison rather than an exact replay.

Upstream CalNode commit e2ce0a72a21b2c1b918cc368132d567c2ff74e44 uses Go MCP SDK v1.8.0 and constructs NewStreamableHTTPHandler with default options. That source observation has not been matched to the exact running edge image.

No booking creation, cancellation, or rescheduling operations were performed during testing.

Steps to reproduce

Reproduce in ChatGPT

  1. Run a self-hosted CalNode instance using the edge Docker image, accessible over HTTPS.
  2. In ChatGPT, configure a custom MCP connection to:
    https://bookings.example.com/mcp
    
  3. Connect using CalNode’s OAuth flow.
  4. Sign in and approve access.
  5. Observe that authentication succeeds, but ChatGPT reports:
    Authentication succeeded, action discovery failed
    
  6. In browser developer tools, inspect the response to:
    POST https://chatgpt.com/backend-api/aip/connectors/links/oauth/callback
    
  7. Observe MCP_ACTION_DISCOVERY_FAILED, with the cause:
    MCP server/discover response was inconsistent from example.com
    

Observe the server-side sequence

Enable access logging for the CalNode site and repeat the connection attempt.

The captured sequence was:

Request HTTP status
GET /oauth/authorize 200
POST /oauth/authorize 302
POST /oauth/token 200
Empty, unauthenticated POST /mcp probe 401
GET /.well-known/oauth-protected-resource 200
GET /.well-known/oauth-authorization-server 200
GET /.well-known/openid-configuration 404
Authenticated POST /mcp, with Mcp-Method: server/discover and Mcp-Protocol-Version: 2026-07-28 200

No further /mcp requests appeared in the captured attempt.

Independently test modern discovery

Replace bookings.example.com with the instance hostname and run:

read -rsp 'CalNode API key: ' calnode_key
echo
curl -sS -i 'https://bookings.example.com/mcp' \
  -H "Authorization: Bearer $calnode_key" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -H 'Mcp-Method: server/discover' \
  --data-binary '{
    "jsonrpc": "2.0",
    "id": "discovery-diagnostic",
    "method": "server/discover",
    "params": {
      "_meta": {
        "io.modelcontextprotocol/protocolVersion": "2026-07-28",
        "io.modelcontextprotocol/clientInfo": {
          "name": "discovery-diagnostic",
          "version": "1.0"
        },
        "io.modelcontextprotocol/clientCapabilities": {}
      }
    }
  }'
unset calnode_key

Observe HTTP 200 and an SSE discovery response with:

{
  "resultType": "complete",
  "supportedVersions": [
    "2025-11-25",
    "2025-06-18",
    "2025-03-26",
    "2024-11-05"
  ]
}

Compare with MCP Inspector

  1. Connect MCP Inspector to the same /mcp endpoint using Streamable HTTP.
  2. Authenticate and connect.
  3. Observe successful initialization with protocol 2025-11-25.
  4. List tools; all ten tools are returned.
  5. Execute list_event_types with {}.
  6. Observe a successful response containing the configured public event types.

Calnode version / commit

edge

How are you running Calnode?

Self-hosted — Docker

Logs, screenshots, or anything else

MCP Inspector successfully connects to the same endpoint using protocol 2025-11-25, discovers all ten tools, and executes list_event_types. This confirms that the older protocol path works with Inspector.

One possibility is that ChatGPT’s current connector discovery flow requires 2026-07-28 and does not accept or fall back to CalNode’s advertised older versions. The captured attempt shows ChatGPT requesting 2026-07-28 and stopping after discovery, with no observable legacy handshake.

This is a hypothesis, not a confirmed ChatGPT requirement. We have not established whether ChatGPT intentionally excludes older versions, has a fallback bug, or rejects another aspect of the discovery response.

The exact response body sent to ChatGPT was not captured. The separate curl reproduction uses an API key rather than ChatGPT’s OAuth token, so it is a comparison rather than an exact replay.

Inspector also flags nullable array schemas such as "type": ["null", "array"] as potentially less portable. These are legal JSON Schema, and there is currently no evidence that they caused this failure: the captured ChatGPT attempt stops before any observable tools/list request.

The deployment uses the moving edge tag; its exact running image digest/commit has not yet been captured. No booking creation, cancellation, or rescheduling operations were performed during testing.

Activity

  1. pullfrog commented on Oct 22, 2026

    @pullfrog
    Contributor
  2. shockalotti commented on Oct 26, 2026

    @shockalotti
    Contributor

    Fixed in #171, merged.

    Your diagnosis was the right thread to pull — it just ended one layer below where you were looking. The SDK does know 2026-07-28 (SEP-2575 server/discover), but it only serves versions at or above 2026-07-28 when the Streamable HTTP transport is stateless:

    // go-sdk v1.8.0
    if version >= protocolVersion20260728 {
        return t.Stateless && slices.Contains(supportedProtocolVersions, version)
    }

    Calnode was passing nil options, i.e. stateful, so the version list was filtered down to the four older ones you captured. Calnode needs no MCP session state — every request is authenticated independently and no tool sends server→client messages — so stateless is a clean fit.

    Your own diagnostic curl now returns, against a fresh build:

    "supportedVersions": ["2026-07-28","2025-11-25","2025-06-18","2025-03-26","2024-11-05"]

    One behaviour change worth knowing: GET and DELETE /mcp now return 405, since there is no session to stream or terminate. Normal initialize → tools/list → tools/call over POST is unchanged and covered by a test.

    Could you reconnect the ChatGPT connector and confirm discovery completes? That is the one step I cannot run from here — everything up to and including the response ChatGPT consumes is verified, but the connector itself is on your side. If it still fails, the next thing worth capturing is the response body ChatGPT actually receives (not just the header/method), since that would tell us whether it is now rejecting something else in the payload.

    Thanks for the thorough write-up — the request table and the MCP Inspector comparison are what made this quick to pin down.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions