chore(chatgpt-mcp): add Deprecation/Sunset headers — retire to mcp.chitty.cc#195
chore(chatgpt-mcp): add Deprecation/Sunset headers — retire to mcp.chitty.cc#195chitcommit wants to merge 1 commit into
Conversation
…itty.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>
|
Warning Rate limit exceeded
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 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
chittyconnect | 174f923 | May 17 2026, 06:53 AM |
There was a problem hiding this comment.
Pull request overview
Adds HTTP deprecation signaling to the legacy ChatGPT MCP route so clients can migrate to the canonical mcp.chitty.cc aggregator before the configured sunset date.
Changes:
- Adds
Deprecation,Sunset, andLinkheaders to all/chatgpt/mcpresponses. - Documents the intended migration target and sunset window inline.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 174f923f1d
ℹ️ 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".
| await next(); | ||
| c.header("Deprecation", "true"); | ||
| c.header("Sunset", "Sat, 15 Aug 2026 00:00:00 GMT"); |
There was a problem hiding this comment.
In chatgptMcp.use, headers are added after await next(), but the downstream handler returns mcpHandler.fetch(...) (a fetch-style Response). In Hono, fetch-returned responses have immutable headers, so calling c.header(...) at this point can raise Can't modify immutable headers and turn valid MCP requests into 500s. This affects normal authenticated traffic hitting /chatgpt/mcp; clone the response (or set headers on a new Response) before mutating headers.
Useful? React with 👍 / 👎.
| // Sunset window: 2026-08-15. | ||
| chatgptMcp.use("*", async (c, next) => { | ||
| await next(); | ||
| c.header("Deprecation", "true"); |
There was a problem hiding this comment.
Deprecation is set to the literal string "true", but the current Deprecation header specification requires a Structured Field Date value; non-compliant values can be ignored by strict clients and tooling, which means automated migration/deprecation handling may not trigger for this endpoint. Use a valid date item (e.g., an @-prefixed Unix timestamp) instead of a boolean string.
Useful? React with 👍 / 👎.
Companion to chittyos/chittymcp#66.
Adds standard deprecation signals on every response from
connect.chitty.cc/chatgpt/mcp: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 the canonical
mcp.chitty.ccaggregator.After sunset (2026-08-15), the McpConnectAgent +
/chatgpt/mcproute +api/routes/chatgpt-mcp.jshandler should be removed from chittyconnect entirely.