OAuth 2.0 Authorization Server Metadata — Petstore MCP Server MCP Resource
OAuth 2.0 Authorization Server Metadata
is one of 3 resources on the
Petstore MCP Server
MCP server. Connect the server and your client can attach it as context.
by client
How to attach OAuth 2.0 Authorization Server Metadata from your client
- Claude Code Petstore MCP Server Resource/OAuth 2.0 Authorization Server Metadata run in your project directory
- Claude Desktop Petstore MCP Server Resource/OAuth 2.0 Authorization Server Metadata ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Petstore MCP Server Resource/OAuth 2.0 Authorization Server Metadata ~/.cursor/mcp.json
- VS Code Petstore MCP Server Resource/OAuth 2.0 Authorization Server Metadata .vscode/mcp.json
- Zed Petstore MCP Server Resource/OAuth 2.0 Authorization Server Metadata ~/.config/zed/settings.json
- Windsurf Petstore MCP Server Resource/OAuth 2.0 Authorization Server Metadata ~/.codeium/windsurf/mcp_config.json
- Cline Petstore MCP Server Resource/OAuth 2.0 Authorization Server Metadata ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Petstore MCP Server Resource/OAuth 2.0 Authorization Server Metadata ~/.gemini/settings.json
- Grok Petstore MCP Server Resource/OAuth 2.0 Authorization Server Metadata .mcp.json (in your project root)
- ChatGPT Petstore MCP Server Resource/OAuth 2.0 Authorization Server Metadata Settings → Connectors → Advanced → Developer mode
- Claude.ai Petstore MCP Server Resource/OAuth 2.0 Authorization Server Metadata Settings → Connectors → Add custom connector
- LangChain Petstore MCP Server Resource/OAuth 2.0 Authorization Server Metadata pip install langchain-mcp-adapters
Other resources on this server
Petstore MCP Server also offers 1 prompt — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.