Skip to content

Commit eaa17c0

Browse files
committed
docs(client): fix crossAppAccess import path
There is no /crossAppAccess subpath export; everything is re-exported from the package root. Collapse into a single import.
1 parent 75212a0 commit eaa17c0

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

docs/client.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -161,8 +161,7 @@ This provider handles a two-step OAuth flow:
161161
2. Exchange the JAG for an access token from the MCP server via RFC 7523 JWT bearer grant
162162

163163
```ts
164-
import { CrossAppAccessProvider } from '@modelcontextprotocol/client';
165-
import { discoverAndRequestJwtAuthGrant } from '@modelcontextprotocol/client/crossAppAccess';
164+
import { CrossAppAccessProvider, discoverAndRequestJwtAuthGrant } from '@modelcontextprotocol/client';
166165

167166
const authProvider = new CrossAppAccessProvider({
168167
// Callback to obtain JWT Authorization Grant
@@ -199,7 +198,7 @@ The `assertion` callback receives a context object with:
199198
- `scope` – Optional scope passed to `auth()` or from `clientMetadata`
200199
- `fetchFn` – Fetch implementation to use for HTTP requests
201200

202-
For manual control over the token exchange steps, use the Layer 2 utilities from `@modelcontextprotocol/client/crossAppAccess`:
201+
For manual control over the token exchange steps, use the Layer 2 utilities from `@modelcontextprotocol/client`:
203202
- `requestJwtAuthorizationGrant()` – Exchange ID Token for JAG at IdP
204203
- `discoverAndRequestJwtAuthGrant()` – Discovery + JAG acquisition
205204
- `exchangeJwtAuthGrant()` – Exchange JAG for access token at MCP server

0 commit comments

Comments
 (0)