Glossary
Resource parameter
An OAuth 2.0 field from RFC 8707 that names the API a token is for. OneLifeVibe always addresses connector tokens to https://onelifevibe.com/mcp.
Updated November 13, 2026
- Standard
- RFC 8707 (Resource Indicators for OAuth 2.0)
- Also called
resource,RFC 8707 resource
At OneLifeVibe
- Tokens for the OneLifeVibe connector are always addressed to https://onelifevibe.com/mcp; the resource parameter may be sent. Access tokens last 5 minutes.
Related terms
What it means
The resource parameter is an OAuth 2.0 request field defined in RFC 8707. It names the API that the requested access token is meant for. You will also see it called the resource indicator. It is not a scope. Scopes describe permissions, while the resource parameter identifies the protected API that should accept the token. The authorization server can use it to set the token's audience, the aud claim. A resource server then checks that audience before accepting the token.
MCP clients may send a resource parameter when they start an OAuth flow. The value is a URI for the target API. Sending it tells the authorization server which API the client intends to call. That helps keep a token from being used against a different service.
How it works
The client adds resource to the authorization request or token request, following RFC 8707. The authorization server decides whether to honor it and can issue an access token whose aud claim matches the named resource. When the client calls the API, the API checks the token audience. If the aud value does not match the API's own identifier, the API should reject the token. This is an audience check, not a permission check.
The parameter does not grant access by itself. Scopes and the authorization server's policy still decide what the token can do. It also does not change where the request goes. The client still sends its HTTP request to the API URL. The resource value is metadata for the token, not a routing instruction.
How OneLifeVibe uses it
For the OneLifeVibe connector, tokens are always addressed to https://onelifevibe.com/mcp. Your MCP client may send the resource parameter, but the audience does not change. The access token is for that MCP endpoint. When you validate a token, compare its audience with https://onelifevibe.com/mcp.
Access tokens for the connector last 5 minutes. Cache the token only for that window and get a new one when it expires. If a call fails with 401, obtain a fresh access token and retry. Do not treat the resource parameter as a way to request a token for another API.
Common mistakes
A common mistake is treating resource as a scope. It does not add permissions. Another is sending a resource value for a different service and expecting OneLifeVibe to issue a token for that service. OneLifeVibe addresses connector tokens to https://onelifevibe.com/mcp.
Some clients omit the parameter and assume the token has no audience. For OneLifeVibe, the token audience is still https://onelifevibe.com/mcp. Validate that value rather than relying on the presence of the request field. Also, do not keep using an access token after its 5 minute lifetime. Get a new one and retry the call.
Questions
Do MCP clients have to send the resource parameter?
MCP clients may send it. For the OneLifeVibe connector, tokens are always addressed to https://onelifevibe.com/mcp whether or not the client includes the field. Validate the token audience against that URL.
What resource value does OneLifeVibe use for connector tokens?
The value is https://onelifevibe.com/mcp. Access tokens for the connector last 5 minutes, so request a new token when the current one expires.
See it working. The OneLifeVibe connector and Platform API put these pieces together.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.