Oauth Scopes Handling logo

Oauth Scopes Handling

Organization
RedHatProductSecurity
oauth-scopes-handling

Handle OAuth scopes in MCP clients according to the WWW-Authenticate header and Protected Resource Metadata discovery flow. Use when building or reviewing MCP client authorization flows, scope negotiation, or permission handling.

Overview

PublisherRedHatProductSecurity
Repositoryprodsec-skills
Skill nameoauth-scopes-handling
Stars
56
Forks
9
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by RedHatProductSecurity on GitHub. Read the source before you install it.

Installation

Install the Oauth Scopes Handling AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/oauth-scopes-handling
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/RedHatProductSecurity/prodsec-skills.git /tmp/prodsec-skills
mkdir -p .claude/skills
cp -r /tmp/prodsec-skills/module/skills/oauth-scopes-handling .claude/skills/oauth-scopes-handling
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Oauth Scopes Handling in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Oauth Scopes Handling on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Oauth Scopes Handling is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

OAuth Scopes Handling in MCP Clients

Security Requirement

MCP clients MUST discover and use OAuth scopes from the WWW-Authenticate header or Protected Resource Metadata when authenticating to MCP servers. Scopes define the permissions the client is requesting and MUST be handled as follows:

Scope Discovery Priority

  1. WWW-Authenticate header: If the MCP client receives a scope parameter in the WWW-Authenticate header of a 401 response, it MUST use those scopes.
  2. Protected Resource Metadata: If no scope is provided in the 401 response, check scopes_supported in the Protected Resource Metadata (PRM) document.

Flow

1. MCP client attempts to access MCP server resource
2. MCP server returns 401 Unauthorized with:
   WWW-Authenticate: Bearer realm="mcp", scope="tools:read tools:execute"
3. MCP client extracts scope from WWW-Authenticate header
   → If scope present: use those scopes for authorization request
   → If scope absent: fetch PRM and use scopes_supported
4. MCP client requests authorization with the discovered scopes

Example: WWW-Authenticate with Scope

http
HTTP/1.1 401 Unauthorized
WWW-Authenticate: Bearer realm="mcp-server",
  scope="tools:read tools:execute resources:read"

The client should request exactly these scopes (or a subset) from the authorization server.

Implementation Checklist

  • Parse scope parameter from WWW-Authenticate header on 401 responses
  • Fall back to scopes_supported from Protected Resource Metadata if no scope in 401
  • Request only the scopes needed for the intended operation (principle of least privilege)
  • Handle scope downgrading by checking granted scopes against requested scopes and disabling features that lack authorization (authorization server may grant fewer scopes)
  • Re-request scopes if the server indicates insufficient permissions on subsequent requests

Frequently asked questions

What does the Oauth Scopes Handling AI skill do?

Handle OAuth scopes in MCP clients according to the WWW-Authenticate header and Protected Resource Metadata discovery flow. Use when building or reviewing MCP client authorization flows, scope negotiation, or permission handling.

Why use Oauth Scopes Handling on TypingMind?

Because you install it once and use it with any model. Oauth Scopes Handling is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Oauth Scopes Handling in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/oauth-scopes-handling. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Oauth Scopes Handling?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Oauth Scopes Handling?

As many as you like. As long as a model supports skills, you can use Oauth Scopes Handling with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Oauth Scopes Handling AI skill free?

Yes. It is published on GitHub by RedHatProductSecurity under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇