- Updated migration guide link in README.md to point to the correct TypeScript v2 documentation.
- Added a new warning banner in docs.json to announce that mcp-use v2 is now in beta.
- Enhanced TypeScript SDK description in docs.json to clarify documentation for both V1 and V2.
- Restructured documentation sections in docs.json for better organization and clarity.
- Replaced logo with a new banner image for better visibility.
- Improved text formatting for readability.
- Updated badge links for npm version and downloads.
- Adjusted Discord badge style for consistency.
- Updated CLI command syntax to include [path] for deployment.
- Improved descriptions for deployment options, including `--name`, `--new`, and `--region`.
- Added `--json` option for machine-readable output and clarified its behavior in the documentation.
- Enhanced error handling and output formatting for better user feedback.
- Updated various command help texts to reflect new features and usage patterns.
- Improved local authentication flow and clarified the behavior of `--no-open` and `--json` options.
- Added tests to ensure correct behavior of new features and error handling.
Drop chalk/cli-highlight from @mcp-use/agent (inline ANSI for prettyStreamEvents), remove the redundant ./browser entry, default autoInitialize in simplified mode, and ship package examples plus corrected install guidance (client is a transitive dep; /langchain is a subpath).
- Updated the API reference to reflect the migration from v1 enum elicitation helpers to Zod form schemas.
- Revised descriptions and examples in the elicitation schemas documentation to guide users on the new Zod-based approach.
- Adjusted links and callouts to emphasize the removal of deprecated v1 helpers and provide migration guidance.
- Renamed `ToolContext` to `RequestContext` in documentation and code.
- Updated the context object to provide enhanced client metadata, including user information and capabilities.
- Improved examples and descriptions for clarity on client capabilities and request-scoped metadata.
- Adjusted tests to reflect changes in client metadata handling and ensure type safety.
Bring back typed Hono routes/middleware with server.fetch as the serving
boundary, restore deprecated response helpers for upgrades, and require
useCallTool names to resolve against mcp-env.d.ts ToolRefs (with
useDynamicTool + mcp-use typecheck as the escape hatch).
* fix inspector hosted proxy and oauth recovery
* remove inspector compatibility report
* refactor(inspector): mount project-local dev inspector
* refactor(inspector): remove CDN application delivery
* fix(inspector): finalize local mount and proxy health checks
* docs(inspector): add self-hosting guide
The inspector README and feature table reference self-hosting with Docker,
but the docs site had no page for it (mcp-use.com/docs/inspector/self-hosting
404s). Add the guide based on the README's self-hosting section: Docker Hub
image, docker run / compose deployment, environment variables, and how
self-hosting compares to the hosted and CLI options.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* docs(inspector): bind examples to loopback, add exposure warning and air-gapped transfer steps
Addresses review feedback on #1861:
- trim wordy intro sentence
- quick start and deployment examples now bind 127.0.0.1 to avoid
exposing the Inspector proxy on all interfaces; added Warning with
reverse-proxy/firewall guidance for remote access
- add docker save/load transfer steps for air-gapped hosts
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: ayaanmacmini3 <ayaanmacmini3@ayaanmacmini3s-Mac-mini.local>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
- Updated documentation to clarify the use of `mcp-use dev --tunnel` and `mcp-use start --tunnel`, including automatic tunnel restart on registration drop.
- Refined TypeScript API references for `allowedOrigins` and `cors` configurations to improve clarity on behavior.
- Transitioned view-related files from `resources/` to `views/`, aligning with new authoring standards.
- Introduced a new `mcp-env.d.ts` for type definitions and simplified favicon selection logic.
- Enhanced the `create-mcp-use-app` template to support views, including a new fruit search example with improved UI components.
- Added mock OpenAI file APIs for local development environments to facilitate testing.
- Updated package.json descriptions and keywords for better clarity and alignment with project goals.
The current mint CLI throws 'URIError: URI malformed' generating the anchor
slug for '### 100% Client Conformance (20/20)' (bare % followed by non-hex),
failing the 'Generate and validate API documentation' job on every PR.
Reworded to 'Full Client Conformance (20/20)'; mint broken-links now passes
across the whole docs tree.
Closes#1911
Co-authored-by: ayaanmacmini3 <ayaanmacmini3@ayaanmacmini3s-Mac-mini.local>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Revamp production view builds to emit hashed assets served over HTTP,
add --with-inspector for build manifests, split MCP_URL from
MCP_ASSETS_URL, and support global CSP env overrides.
- Replaced existing SVG logos and favicon with new designs featuring updated dimensions and styles.
- Enhanced the visual representation of the assets to align with the current branding guidelines.
- Added a new `langchain.ts` file to the agent package for LangChain integration, including necessary exports and configurations.
- Updated package.json and tsup.config.ts to reflect new entry points and dependencies.
- Added a new migration page to the TypeScript client documentation for better guidance on transitioning between versions.
- Updated descriptions in various documentation files to improve clarity and consistency, including the MCPClient and Code Mode sections.
- Revised links and examples to ensure they reflect the latest structure and best practices for using the MCP client.
- Removed redundant version generation command for @mcp-use/client in the CI workflow.
- Updated documentation links in code-mode.mdx and other files to reflect new paths.
- Changed installation instructions from yarn to npm for consistency across documentation.
- Enhanced error handling in client authentication and session management.
- Added a utility function to compare semantic versions in telemetry.
- Removed outdated unit tests for FileKVStore.
- Improved formatting and consistency in README.md and various documentation files.
- Updated import paths to reflect the new package structure for @mcp-use/client and @mcp-use/agent.
- Enhanced examples and descriptions for MCPAgent and related components.
- Cleaned up whitespace and formatting for better readability across multiple files.
* fix(auth): re-anchor proxy-origin .well-known discovery onto the MCP server (#1843)
* fix(auth): re-anchor proxy-origin .well-known discovery onto the MCP server
MCP traffic must always go through the gateway/inspector proxy (browser CORS
on direct connections cannot be guaranteed — edge errors bypass the gateway's
CORS middleware). But with the transport connected to the proxy URL, the SDK
derives /.well-known/* discovery URLs from the proxy origin whenever no
resource_metadata hint is available (SSE EventSource cannot read
WWW-Authenticate; token refresh runs without a 401 at hand). Discovery then
failed on the proxy origin and the server was misclassified as "does not
support OAuth", hiding the Authenticate button on gateway-hosted servers.
BrowserOAuthClientProvider.getProxyFetch() now rewrites connection-origin
.well-known lookups onto the actual MCP server before routing them through
the OAuth proxy — reproducing exactly what a direct connection would request,
including the RFC 8414 §3.1 / RFC 9728 §3.1 path-insertion form.
* style: prettier format
* chore: enter canary prerelease mode
* chore(typescript): version packages (canary)
* docs(changelog): add v1.34.1 (hosted OAuth discovery through the proxy)
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* fix(client): wire oauthProxyUrl option + stop misclassifying discovered OAuth servers (#1840)
Hosted OAuth servers (e.g. gateway-fronted, custom-domain) were dropping to
`failed` with "Server does not support OAuth", hiding the Authenticate button.
Routing MCP traffic through the inspector proxy anchored OAuth discovery on the
proxy origin; a secondary discovery pass (token refresh / SSE fallback) then hit
an HTML/500 and matched isOAuthDiscoveryFailure().
- Fully wire UseMcpOptions.oauthProxyUrl through createBrowserOAuthProvider so
OAuth traffic can be proxied for CORS while MCP stays direct (transparent
proxy preserves RFC 8414 issuer validation). preventAutoAuth manual flow now
always uses the scoped OAuth proxy fetch instead of the MCP gateway proxy.
- useMcp: when a prepared authorization URL already exists (OAuth discovery
succeeded on an earlier pass) and preventAutoAuth is set, surface
`pending_auth` on a later failure instead of "server does not support OAuth".
* chore: enter canary prerelease mode
* chore(typescript): version packages (canary)
* docs: update changelogs for v12.0.0 and v1.34.0 releases
- Added details for v12.0.0, highlighting improvements in hosted OAuth reliability and updates from `mcp-use` v1.34.0.
- Included fixes for OAuth server failures and updates to peer dependencies in the inspector changelog.
- Documented new features and fixes in the TypeScript changelog, emphasizing the introduction of `oauthProxyUrl` for enhanced OAuth proxying and reliability improvements.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Enrico Toniato