@raybase/create 0.3.25 → 0.3.26

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
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@raybase/create",
3
- "version": "0.3.25",
3
+ "version": "0.3.26",
4
4
  "description": "Scaffold secure internal apps powered by Raybase.",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -74,9 +74,12 @@ app's connector, and what the app controls:
74
74
  and its colours are `--rb-consent-*` custom properties. For a page of the
75
75
  app's own, set `mcp.consent.path`: consent is sent there with the request's
76
76
  query, the page reads `GET /api/auth/oauth/consent` with the same query
77
- (client and connector names, scopes, a description, an optional `choice`,
78
- and the `fields` to post) and posts the fields plus `decision=approve` or
79
- `deny` to `/api/auth/oauth/authorize`. Unsigned visitors get 401 with
77
+ (client and connector names, scopes, a description, `returnsTo`, an
78
+ optional `choice`, and the `fields` to post) and posts the fields plus
79
+ `decision=approve` or `deny` to `/api/auth/oauth/authorize`. `returnsTo` is
80
+ where the sign-in code goes (the redirect URI's scheme, host and port, in
81
+ full, since a loopback redirect matches any port): the built-in page names
82
+ it, and an app's own page should too. Unsigned visitors get 401 with
80
83
  `signIn`, the address to send them to.
81
84
  - **Standing instructions.** `mcp.instructions` is returned from
82
85
  `initialize`. Products keep only the start (512 to 4,096 characters), so
@@ -111,7 +114,13 @@ export const appConfig = {
111
114
  ```
112
115
 
113
116
  Use hostnames, not full redirect URLs. Include only clients the owner intends
114
- to trust. For internal apps that should not accept new OAuth clients at
117
+ to trust. Whatever the list (`["*"]` included), a client's metadata document
118
+ and its `client_uri`, `logo_uri`, `tos_uri` and `policy_uri` must not be at a
119
+ private address: they are judged as every outbound fetch is
120
+ (`validateOutboundHttpsUrl`: localhost, metadata names, and every loopback,
121
+ private, link-local and special-purpose literal, IPv6 and mapped IPv4
122
+ included). Workers cannot see what a name resolves to, so the list is the
123
+ only guard against a public name that points somewhere private. For internal apps that should not accept new OAuth clients at
115
124
  runtime, disable Dynamic Client Registration instead:
116
125
 
117
126
  ```ts
@@ -300,6 +309,11 @@ the `io.modelcontextprotocol/ui` extension and accept
300
309
  (and `raybase dev` at startup) warns with `mcp-tool-scopes`. For a tool a
301
310
  person's agent should use, declare no scopes or only `mcp:read`/`mcp:write`;
302
311
  for one kept for the app's own services, declare only the app's own scopes.
312
+ - In an app whose every tool is meant for agents people approve (a
313
+ platform's store apps, say), set `mcp: { appOnlyTools: false }`. Doctor
314
+ then fails (`mcp-tool-scopes`, error) on any tool no person's agent can
315
+ reach, including one that declares only an app-only scope such as
316
+ `mcp:shopify:products:read`.
303
317
  - Operator scopes must stay on Operator MCP. App MCP grants must never request
304
318
  `operator:*` scopes.
305
319