@raybase/create 0.3.21 → 0.3.23
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -294,6 +294,12 @@ the `io.modelcontextprotocol/ui` extension and accept
|
|
|
294
294
|
`mcpAppConnectorScopeOptions()`, or Pro's `createRaybaseMachineCredential`).
|
|
295
295
|
Registration, consent and the token endpoint answer any other scope with
|
|
296
296
|
`invalid_scope`.
|
|
297
|
+
- So a list of alternatives is a trap: `scopes: ["mcp:read", "acme:x"]` or
|
|
298
|
+
`scopes: ["mcp:read", "mcp:tool:<name>"]` needs every one, and no agent a
|
|
299
|
+
person approves ever sees the tool, with nothing failing. `raybase doctor`
|
|
300
|
+
(and `raybase dev` at startup) warns with `mcp-tool-scopes`. For a tool a
|
|
301
|
+
person's agent should use, declare no scopes or only `mcp:read`/`mcp:write`;
|
|
302
|
+
for one kept for the app's own services, declare only the app's own scopes.
|
|
297
303
|
- Operator scopes must stay on Operator MCP. App MCP grants must never request
|
|
298
304
|
`operator:*` scopes.
|
|
299
305
|
|