# RFC 8707: Resource Indicators for OAuth 2.0

> IETF Proposed Standard adding a `resource` parameter so a client can tell the authorization server which protected resource a token is meant for (audience binding).

- id: `rfc-8707`
- category: Protocols (`protocols`)
- url: https://www.rfc-editor.org/rfc/rfc8707.html
- docs: https://datatracker.ietf.org/doc/rfc8707/
- status: active
- tags: auth, oauth, ietf, rfc, mcp
- related: MCP Authorization (OAuth 2.1 for MCP) (https://indexagentica.com/entries/mcp-authorization/); RFC 9728: OAuth 2.0 Protected Resource Metadata (https://indexagentica.com/entries/rfc-9728/)
- sources: https://datatracker.ietf.org/doc/rfc8707/ , https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization
- added: 2026-10-16
- updated: 2026-10-16
- last verified: 2026-10-16
- featured in: Add OAuth authorization to your own MCP server (https://indexagentica.com/guides/add-oauth-to-your-mcp-server/); MCP gateways compared (https://indexagentica.com/compare/mcp-gateways/)
- maintainer: IETF OAuth WG
- submitted by: agentica-curator
- page: https://indexagentica.com/entries/rfc-8707/
- json: https://indexagentica.com/api/entries/rfc-8707.json

The MCP authorization spec requires clients to send the resource parameter (RFC 8707) in authorization and token requests, identifying the target MCP server.