[dependabot]

Bumps @modelcontextprotocol/server to 2.3.1 and updates ancestor dependency @angular/cli. These dependencies need to be updated together.

Updates @modelcontextprotocol/server from 2.0.0 to 2.3.1

Release notes

Sourced from @​modelcontextprotocol/server's releases.

@​modelcontextprotocol/server-legacy@​2.3.1

Patch Changes

• #2952 5a18673 Thanks @​claude! - requireBearerAuth in @modelcontextprotocol/server-legacy takes the optional expectedResource that @modelcontextprotocol/server 2.3.0 and @modelcontextprotocol/sdk 1.32.0 added: the resource the token must be issued for (its audience), usually the server's URL. When it is set, a token is accepted only if the verifier reports that value in AuthInfo.resource; the two are compared as strings, ignoring a fragment and one trailing slash. A token reported for another value, or for none, is answered 401 invalid_token with the usual WWW-Authenticate challenge. When it is not set, nothing changes. The package stays frozen otherwise; this option is added so that its requireBearerAuth matches the 1.x middleware it is a copy of.

• Updated dependencies []:

  • @​modelcontextprotocol/core@​2.3.1

@​modelcontextprotocol/server@​2.3.1

Patch Changes

• Updated dependencies []:
  • @​modelcontextprotocol/core@​2.3.1

@​modelcontextprotocol/server-legacy@​2.3.0

Patch Changes

• #2908 633dd3e Thanks @​claude! - The license field of the package manifests is now Apache-2.0; the LICENSE file shipped in each package carries the full terms, including the MIT text for earlier contributions. No code change.

• Updated dependencies [633dd3e]:

  • @​modelcontextprotocol/core@​2.3.0

@​modelcontextprotocol/server@​2.3.0

Minor Changes

• #2929 40f8f4e Thanks @​claude! - requireBearerAuth and verifyBearerToken take a new optional expectedResource, which makes them accept only tokens issued for this resource (the token's audience). Set it to the value your authorization server puts into tokens meant for this server, usually the server's URL. When it is set, a token is accepted only if the verifier reports that value in AuthInfo.resource; the two are compared as strings, ignoring a fragment and one trailing slash. A token reported for another value, or for none, is answered 401 invalid_token with the usual WWW-Authenticate challenge. When it is not set, nothing changes. To use it, pass expectedResource and have verifyAccessToken fill AuthInfo.resource, for example from the aud claim. The option is declared on a new exported type, VerifyBearerTokenOptions, which extends BearerAuthOptions; BearerAuthOptions itself is unchanged. The Express requireBearerAuth passes the option through. With Express, @modelcontextprotocol/express has to be upgraded to this release as well: 2.0.1 does not pass the option on, so nothing is compared. Its options type does not have the option, so TypeScript reports an expectedResource written in a call to the 2.0.1 requireBearerAuth as an error.

• #2926 6d8dbc6 Thanks @​claude! - McpServer now accepts a maxToolInputElements option that limits the number of elements in tool-call arguments: the largest combined number of array elements and object members a single tools/call arguments payload may contain. It is off by default, so behavior is unchanged unless you set it. When it is set and a call exceeds it, that call is answered with an isError: true tool result that names the limit, before the input schema runs, and the server keeps serving. Set it above the largest arguments your tools legitimately accept; maxRequestBodySize remains the primary limit on request size. The value must be a number of at least 1, or Infinity for no limit; any other value is rejected at construction. The options type is exported as McpServerOptions.

• #2918 84804c2 Thanks @​claude! - A Server or McpServer now serves one connection at a time, and a Streamable HTTP server transport without sessions (sessionIdGenerator: undefined) serves one request. An app that uses one server object, or one stateless transport, for every HTTP request fails on the second request after this upgrade. Build the server and the transport per request instead.

  What keeps working without a change:

  • createMcpHandler(buildServer) and serveStdio(buildServer), where buildServer returns a new server on every call.
  • A handler that builds a new server and a new stateless transport for each request.
  • One server and one transport per session (a transport with a sessionIdGenerator).
  • Connecting a server again after close().
  • Client.

  What fails now, how it shows, and what to change:

  • One server object with a new stateless transport per request (const server = new McpServer(...) outside the handler, await server.connect(transport) inside it): the second HTTP request the process receives fails, and so does every later one. connect() rejects with an SdkError of code ALREADY_CONNECTED. If the handler closes the transport when the response ends, requests that arrive one after the other still work and a request that overlaps another one fails. Change: move new McpServer(...) and its registrations into the handler.
  • One stateless transport for every request (a transport built once with sessionIdGenerator: undefined): the second HTTP request fails. WebStandardStreamableHTTPServerTransport.handleRequest() rejects with Stateless transport cannot be reused across requests. Create a new transport per request., and NodeStreamableHTTPServerTransport.handleRequest() answers 500. Change: build the server and the transport inside the handler and connect them there.
  • createMcpHandler(() => server) with a server built once: a request that arrives after the previous response has been read to its end still works. A request that arrives while another one is being served is answered 500 with the JSON-RPC error -32603 (Internal server error); the reason is reported only through the onerror option. Change: pass a function that builds the server, as in createMcpHandler(buildServer).
  • One server object for every session: the initialize request of the second session fails with ALREADY_CONNECTED. Change: build a server per session.

  What the caller sees when connect() or handleRequest() rejects depends on the host. Express 5, Fastify and Hono answer 500. A plain node:http listener without its own error handling gets an unhandled rejection, which ends the process.

  The README examples of @modelcontextprotocol/express, @modelcontextprotocol/fastify, @modelcontextprotocol/hono and @modelcontextprotocol/node, and the handler examples in the JSDoc of WebStandardStreamableHTTPServerTransport and NodeStreamableHTTPServerTransport, now build a server and a transport per request.

• #2907 e55f9ac Thanks @​claude! - allowedOrigins and validateOriginHeader accept lowercase entries of the form <scheme>://*, such as moz-extension://* or chrome-extension://*, which admit every origin of that scheme. This lets a server admit MCP clients that run as a browser extension when the extension ID cannot be listed, as on Firefox, where it differs on every install. http://* and https://* are not honoured, and the defaults are unchanged.

... (truncated)

Commits

• fcef852 Version Packages (#2953)
• e8b7f05 docs: one opening note in the server and client package READMEs (#2955)
• 5a18673 feat(server-legacy): add expectedResource to requireBearerAuth (#2952)
• 3ab61c6 docs: update the README banners (#2940)
• 8aabbdc test(e2e): expect SdkHttpError after a second 401 from onUnauthorized (#2936)
• 33fecfb test(e2e): cover tools/call without arguments (#2933)
• 818f782 docs: state the principles in CLAUDE.md and shorten REVIEW.md (#2938)
• a202a36 Version Packages (#2896)
• 2d731fa fix(client): refresh again when an SSE retry failed for a reason other than 4...
• b6e5c55 test(e2e): cover prompts/get without arguments for prompts with a schema (#2928)
• Additional commits viewable in compare view

Updates @angular/cli from 22.2.1 to 22.2.3

Release notes

Sourced from @​angular/cli's releases.

22.2.3

@​schematics/angular

Commit	Description
	keep the workspace build version in the use-application-builder migration

@​angular/cli

Commit	Description
	accept multi-digit array indices in ng config
	keep ng version working when the package manager is not installed
	resolve package name in npm workspace members

@​angular-devkit/schematics

Commit	Description
	avoid stack overflow when chaining many rules

@​angular/build

Commit	Description
	add CSP nonce to stylesheet and modulepreload link elements
	always use AOT when extracting i18n messages
	coalesce external watcher directories to avoid macOS FSEvents limit
	disable Vitest fsModuleCache in unit-test builder
	ensure Sass importers return global Promise instances
	keep Vite server file watcher disabled in Vitest watch mode
	sort discovered unit-test files for deterministic builds
	use module.registerHooks() for in-memory ESM loader
	avoid invalidating Angular diagnostic cache on stylesheet change
	resolve asset patterns concurrently with bounded concurrency

@​angular/ssr

Commit	Description
	preserve preload metadata for nested empty-path routes
	preserve query parameters on relative route redirects
	resolve relative redirects against the parent route

22.2.2

@​angular-devkit/build-angular

Commit	Description
	preserve Host header when proxying in ssr-dev-server

@​angular/build

Commit	Description
	keep the order of glob entries in the proxy configuration
	support a string context in array-form proxy configurations

Changelog

Sourced from @​angular/cli's changelog.

22.2.3 (2026-10-15)

@​angular/cli

Commit	Type	Description
3158e865f	fix	accept multi-digit array indices in ng config
bcff0e76a	fix	keep ng version working when the package manager is not installed
5570c91d2	fix	resolve package name in npm workspace members

@​schematics/angular

Commit	Type	Description
881865f36	fix	keep the workspace build version in the use-application-builder migration

@​angular-devkit/schematics

Commit	Type	Description
cf1f3b9d4	fix	avoid stack overflow when chaining many rules

@​angular/build

Commit	Type	Description
1d477d6bc	fix	add CSP nonce to stylesheet and modulepreload link elements
fbe208f83	fix	always use AOT when extracting i18n messages
c1c4216a6	fix	coalesce external watcher directories to avoid macOS FSEvents limit
792990bc2	fix	disable Vitest fsModuleCache in unit-test builder
82439399c	fix	ensure Sass importers return global Promise instances
a818de415	fix	keep Vite server file watcher disabled in Vitest watch mode
91bad469e	fix	sort discovered unit-test files for deterministic builds
e84db4af7	fix	use module.registerHooks() for in-memory ESM loader
a428021b7	perf	avoid invalidating Angular diagnostic cache on stylesheet change
b0ac394a0	perf	resolve asset patterns concurrently with bounded concurrency

@​angular/ssr

Commit	Type	Description
bd09b98fc	fix	preserve preload metadata for nested empty-path routes
a92546892	fix	preserve query parameters on relative route redirects
a2b86cc94	fix	resolve relative redirects against the parent route

21.2.27 (2026-10-14)

... (truncated)

Commits

• afa3814 release: cut the v22.2.3 release
• cc05ecf build: update pnpm to v12.11.2
• c1c4216 fix(@​angular/build): coalesce external watcher directories to avoid macOS FSE...
• 116cb93 build: update cross-repo angular dependencies
• e84db4a fix(@​angular/build): use module.registerHooks() for in-memory ESM loader
• cf1f3b9 fix(@​angular-devkit/schematics): avoid stack overflow when chaining many rules
• 91bad46 fix(@​angular/build): sort discovered unit-test files for deterministic builds
• bd09b98 fix(@​angular/ssr): preserve preload metadata for nested empty-path routes
• 9313776 build: lock file maintenance
• c0b6659 build: update dependency zod to v4.6.6
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.