mirror of
https://github.com/mcp-use/mcp-use.git
synced 2026-09-14 18:06:01 +08:00
Andrew Khadder
1af9bebce5
* feat(client): support RequestOptions for prompt reads (#2302) * feat(client): support request options for prompts * Apply suggestion from @cubic-dev-ai[bot] Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com> Signed-off-by: Andrew Khadder <54488379+khandrew1@users.noreply.github.com> --------- Signed-off-by: Andrew Khadder <54488379+khandrew1@users.noreply.github.com> Co-authored-by: Andrew Khadder <54488379+khandrew1@users.noreply.github.com> Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com> * chore: enter canary prerelease mode * chore(typescript): version packages (canary) * feat(inspector): correlate RPC response labels (#2303) * feat(inspector): correlate RPC response labels * fix(inspector): refine RPC latency label styling * chore(typescript): version packages (canary) * fix(server): restore Claude resource domain hashing in v2 (#2326) * fix(server): restore Claude resource domain hashing in v2 v1.29.0 rewrote a view resource's `_meta.ui.domain` to `<sha256(domain)[0..32]>.claudemcpcontent.com` when the reading client advertised a name containing "claude". The v2 rewrite dropped that along with the v1 server package, so Claude receives the authored `view.domain` verbatim and refuses to render the view. Restore the three helpers in `src/views/claude-domain.ts`. The digest and the substring match are byte-for-byte the v1 ones, so a server upgrading from v1 emits the same domain it did before; the v1 fixtures are ported as unit tests. The digest uses Web Crypto rather than `node:crypto` to keep the root module graph free of Node builtins for the Workers build. Client identity reaches the `resources/read` handler through the per-request `_meta` envelope (`io.modelcontextprotocol/clientInfo`) — the same source `ctx.client.info()` already reads, extracted as `requestClientInfo()` in `src/context.ts`. Non-Claude clients, an already-hashed authored domain, and `resources/list` are all unchanged, matching v1. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BAiXkmFngnfwhAeNuDbFKg * docs(v2): drop the stale per-client View metadata limitation The v2 migration guide's beta-limitations list stated that "v2 has no supported hook for rewriting `domain` or other View resource metadata per client". Restoring the Claude resource domain hashing makes that false — `_meta.ui.domain` is now derived per requesting client on `resources/read`. Remove the bullet outright rather than softening it. The rest of the Views limitations list is unaffected and reads cleanly without it; the `resources/list` and authoring surfaces it also described are covered by the resource-facts guidance earlier in the same guide. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BAiXkmFngnfwhAeNuDbFKg * fix(server): detect legacy Claude clients by user agent * fix(server): lazy-load the Claude domain helper to stay under the edge budget `tests/budgets/cli-budget.test.ts` caps the edge entry's static graph at 120 KiB. Statically importing `views/claude-domain.js` from `server.ts` put the graph at 123061 bytes, 181 over the cap, failing CI on this branch (`main` sits at 121721, so the branch consumed all 1159 bytes of headroom). The `resources/read` callback is already async, so the helper loads through a dynamic import at its one call site instead, matching the lazy-loading the same budget test enforces for the CLI commands. The re-export from `views/index.ts` is dropped so the module leaves the static graph; the unit tests already import it from `views/claude-domain.js` directly. Behavior is unchanged — the user-agent fallback and the hash are untouched. Edge static graph: 123061 -> 122208 bytes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BAiXkmFngnfwhAeNuDbFKg * fix(server): keep Claude domain helper in edge graph --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Andrew Khadder <andrew@manufact.com> * chore(typescript): version packages (canary) * docs: update TypeScript release changelogs --------- Signed-off-by: Andrew Khadder <54488379+khandrew1@users.noreply.github.com> Co-authored-by: WeiHaoxuan <156066259+Whxuan0701@users.noreply.github.com> Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com> Co-authored-by: Claude <noreply@anthropic.com>
Mintlify Starter Kit
Click on Use this template to copy the Mintlify starter kit. The starter kit contains examples including
- Guide pages
- Navigation
- Customizations
- API Reference pages
- Use of popular components
Development
Install the Mintlify CLI to preview the documentation changes locally. To install, use the following command
npm i -g mintlify
Run the following command at the root of your documentation (where docs.json is)
mintlify dev
Publishing Changes
Install our Github App to auto propagate changes from your repo to your deployment. Changes will be deployed to production automatically after pushing to the default branch. Find the link to install on your dashboard.
Troubleshooting
- Mintlify dev isn't running - Run
mintlify installit'll re-install dependencies. - Page loads as a 404 - Make sure you are running in a folder with
docs.json