ChatGPT's API docs recommend library fields that don't exist (community.openai.com)

A developer reports that the ChatGPT Apps SDK documentation shows an example using a tool-level securitySchemes field (e.g., [{type: "noauth"}, {type: "oauth2", scopes: ["search.read"]}]) to declare auth requirements, but that field does not exist in the referenced Model Context Protocol (MCP) TypeScript library nor in the FastMCP Python client. They’re stuck trying to implement OAuth and persistent storage between chats (needed for anything beyond ephemeral demos), hitting vague connection errors and missing concrete examples or tutorials for MCP + OAuth newcomers. This mismatch matters because clear, accurate SDK docs are critical for implementing secure OAuth flows and persistent user data in Apps SDK integrations. If docs and published libraries diverge, developers waste time, can't rely on declarative auth primitives, and are forced to implement custom server-side auth and storage workarounds. Technical implications: check SDK/library version alignment, inspect the MCP server implementation for supported auth fields, raise issues on the SDK repo, or implement OAuth handling and persistence on your own backend until the SDK is updated. The post also calls for a built-in persistent storage option in the Apps SDK to simplify common use cases (avoid requiring external servers and account creation), which would significantly lower the barrier for building useful apps.