Skip to content

chore(chatgpt-gateway): add Deprecation/Sunset headers — retire to mcp.chitty.cc - #66

Merged
chitcommit merged 1 commit into
mainfrom
chore/deprecate-chatgpt-gateway
May 23, 2026
Merged

chore(chatgpt-gateway): add Deprecation/Sunset headers — retire to mcp.chitty.cc#66
chitcommit merged 1 commit into
mainfrom
chore/deprecate-chatgpt-gateway

Conversation

@chitcommit

Copy link
Copy Markdown
Contributor

Summary

Emit standard deprecation signals on the ChatGPT-specific MCP gateway. ChatGPT MCP doesn't require a unique hostname — the OpenAI spec only needs a valid OAuth issuer + MCP transport, both already on the canonical `mcp.chitty.cc` aggregator with broader scope coverage and unified audit.

Headers added (every response)

```
Deprecation: true
Sunset: Sat, 15 Aug 2026 00:00:00 GMT
Link: https://mcp.chitty.cc/mcp; rel="successor-version",
https://mcp.chitty.cc/sse; rel="alternate"
```

Retirement plan

  1. Merge + deploy this PR → ChatGPT clients see deprecation signals.
  2. Add `mcp.chitty.cc` to ChatGPT Connector config; OAuth flow auto-registers via `/register`.
  3. Watch traffic shift from `mcp-chatgpt.chitty.cc` → `mcp.chitty.cc`.
  4. After 2026-08-15: delete CF route `7de271ce55d64215b3d89f8e5c49309b`, delete `chittymcp-gateway` worker, delete `mcp-gateway- chatgpt/` subtree.

Companion PR

chittyos/chittyconnect#TBD also adds deprecation headers to `connect.chitty.cc/chatgpt/mcp` (same retirement target).

No tool/protocol behavior changes; pure response-header addition.

…p.chitty.cc

ChatGPT MCP doesn't actually require a unique hostname — the OpenAI MCP
spec only needs a valid OAuth issuer + MCP transport endpoint, both of
which the canonical mcp.chitty.cc aggregator already exposes (with
broader scope coverage and unified audit).

Emit standard deprecation signals (RFC 8594 / draft-ietf-httpapi-deprecation)
on every response from this gateway:
  Deprecation: true
  Sunset: Sat, 15 Aug 2026 00:00:00 GMT
  Link: <https://mcp.chitty.cc/mcp>; rel="successor-version",
        <https://mcp.chitty.cc/sse>; rel="alternate"

Sunset window: ~3 months for ChatGPT-registered clients to re-discover
the canonical issuer at mcp.chitty.cc/.well-known/oauth-authorization-server
and dynamic-register fresh credentials. After sunset, this subtree +
the mcp-chatgpt.chitty.cc/* route + the chittymcp-gateway worker should
be removed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented May 17, 2026

Copy link
Copy Markdown
Contributor

Warning

Rate limit exceeded

@chitcommit has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 50 minutes and 23 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 446145cb-59c6-4dfa-a08f-316cfdc2618a

📥 Commits

Reviewing files that changed from the base of the PR and between 9312629 and e20e119.

📒 Files selected for processing (1)
  • mcp-gateway- chatgpt/src/index.js
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/deprecate-chatgpt-gateway

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions

Copy link
Copy Markdown

@coderabbitai review
@copilot review
Adversarial review request: evaluate security, policy bypass paths, and regression risk.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e20e11962f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread mcp-gateway- chatgpt/src/index.js
Comment thread mcp-gateway- chatgpt/src/index.js
@chitcommit
chitcommit enabled auto-merge (squash) May 23, 2026 12:13
@chitcommit
chitcommit merged commit c10b24d into main May 23, 2026
13 checks passed
@chitcommit
chitcommit deleted the chore/deprecate-chatgpt-gateway branch May 23, 2026 12:36
chitcommit added a commit to chittyos/chittyconnect that referenced this pull request Jun 16, 2026
…itty.cc (#195)

* chore(chatgpt-mcp): add Deprecation/Sunset headers — retire to mcp.chitty.cc

The /chatgpt/mcp route inside chittyconnect duplicates capability that
belongs at the canonical mcp.chitty.cc aggregator. ChatGPT MCP doesn't
require a unique hostname or carve-out — the OpenAI spec only needs a
valid OAuth issuer + MCP transport, both already on mcp.chitty.cc with
unified audit.

Emit standard deprecation signals (RFC 8594) on every response:
  Deprecation: true
  Sunset: Sat, 15 Aug 2026 00:00:00 GMT
  Link: <https://mcp.chitty.cc/mcp>; rel="successor-version",
        <https://mcp.chitty.cc/sse>; rel="alternate"

After sunset, the McpConnectAgent + the /chatgpt/mcp route + the
api/routes/chatgpt-mcp.js handler should be removed from chittyconnect.

Companion PR: chittyos/chittymcp#66 (mcp-chatgpt.chitty.cc gateway).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* fix(chatgpt-mcp): rebuild response for headers + RFC 9745 Deprecation date

Address PR #195 review:
- P1: clone the Response before setting deprecation headers — the downstream
  MCP handler returns a streamed/immutable Response and in-place header
  mutation can throw.
- P2: Deprecation header now uses RFC 9745 structured-field Date (@unix-seconds)
  instead of the legacy boolean "true".

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant