openai-apps-sdk-oauth

Implement OAuth 2.1 authentication and per-tool securitySchemes for MCP-backed apps.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/pingqLIN/UniText --skill openai-apps-sdk-oauth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openai-apps-sdk-oauth
Source: https://github.com/pingqLIN/UniText/tree/main/runtime/skills/openai-apps-sdk-oauth
Command: npx skills add https://github.com/pingqLIN/UniText --skill openai-apps-sdk-oauth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

OpenAI Apps SDK OAuth enables secure, standardized authentication and account linking for MCP-backed websites, servers, and ChatGPT apps by implementing OAuth 2.1 flows, protected-resource metadata, and per-tool access controls.

Core Features & Use Cases

  • OAuth 2.1 integration for Apps SDK authentication across website, MCP server, and ChatGPT apps
  • Per-tool securitySchemes to enforce access at the tool level
  • Publication of protected-resource metadata and token verification guidance for the MCP
  • Clear workflow guidance for architecture decisions, testing, and rollout

Quick Start

Configure your MCP environment and identity provider to support OAuth 2.1 per the OpenAI Apps SDK guidelines, wire protected-resource metadata, and enable per-tool security schemes.

Frequently Asked Questions about openai-apps-sdk-oauth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement OAuth 2.1 authentication for an MCP-backed ChatGPT app?

Implement OAuth 2.1 authentication for MCP-backed ChatGPT apps by configuring your identity provider, wiring protected-resource metadata, and enabling per-tool security schemes to manage account linking securely.

What is protected-resource metadata in the OpenAI Apps SDK?

Protected-resource metadata in the OpenAI Apps SDK is a published standard that defines how MCP servers expose token verification endpoints and security configurations for authenticating client applications.

How do I enforce per-tool securitySchemes in an MCP server?

Enforce per-tool securitySchemes in an MCP server by defining access controls at the tool level, ensuring each tool validates OAuth 2.1 tokens independently before executing protected resource operations.

Do I need token verification checks for every tool in my MCP server?

Token verification checks are required for protected MCP server tools. Per-tool securitySchemes allow you to specify which tools demand OAuth 2.1 token validation and which remain publicly accessible to clients.

What are the limitations of using OAuth 2.1 with the Apps SDK for MCP?

Limitations of using OAuth 2.1 with the Apps SDK include the strict requirement for protected-resource metadata publication and the need for an identity provider supporting the full OAuth 2.1 specification.