Skip to content

docs: clarify ChatGPT Site tools compatibility - #11

Merged
TueJon merged 2 commits into
mainfrom
fix/webmcpify-state-of-art-20260831
Aug 31, 2026
Merged

docs: clarify ChatGPT Site tools compatibility#11
TueJon merged 2 commits into
mainfrom
fix/webmcpify-state-of-art-20260831

Conversation

@TueJon

@TueJon TueJon commented Aug 31, 2026

Copy link
Copy Markdown
Owner

Summary

  • date the ChatGPT Site tools compatibility snapshot to 2026-08-31
  • document that the built-in browser currently discovers top-level imperative tools, not declarative forms or iframe registrations
  • keep that client subset distinct from the broader WebMCP APIs verified in Chrome

Primary evidence: https://learn.chatgpt.com/docs/webmcp

Verification

  • npm run check
  • 19 tests passed; TypeScript and JavaScript syntax checks passed
  • npm audit: 0 vulnerabilities

@TueJon TueJon added documentation Improvements or additions to documentation webmcp WebMCP agent surface labels Aug 31, 2026
@TueJon TueJon self-assigned this Aug 31, 2026
@TueJon TueJon added documentation Improvements or additions to documentation webmcp WebMCP agent surface labels Aug 31, 2026

@TueJon TueJon left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

No blocking findings. The top-level imperative-only Site tools boundary matches OpenAI's current documentation, and the four changed docs remain internally consistent.
Reviewed exact head 6c89309d18ad4731469707568877a439e4f62153; 0 findings.

@TueJon
TueJon merged commit 1a7053f into main Aug 31, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation webmcp WebMCP agent surface

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant