Skip to content

build: update dependency @ai-sdk/mcp to v2 - #291

Open
angular-robot wants to merge 1 commit into
angular:mainfrom
angular-robot:ng-renovate/ai-sdk-mcp-2-x
Open

build: update dependency @ai-sdk/mcp to v2#291
angular-robot wants to merge 1 commit into
angular:mainfrom
angular-robot:ng-renovate/ai-sdk-mcp-2-x

Conversation

@angular-robot

@angular-robot angular-robot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@ai-sdk/mcp (source) 1.0.302.0.39 age adoption passing confidence

  • If you want to rebase/retry this PR, check this box

Release Notes

vercel/ai (@​ai-sdk/mcp)

v2.0.39

Compare Source

Patch Changes

v2.0.37

Compare Source

Patch Changes

v2.0.36

Compare Source

Patch Changes

v2.0.35

Compare Source

Patch Changes
  • 76fb75d: fix(mcp): reject SSE requests when POST responses are unsuccessful

v2.0.34

Compare Source

Patch Changes

v2.0.33

Compare Source

Patch Changes
  • 1f29230: feat(mcp): harden oauth client registration according to latest protocol
  • 0c60a40: feat(mcp): add mcp 2026 streamable HTTP support
  • e6a9927: feat(mcp): add the latest 2026 protocol discovery foundation

v2.0.32

Patch Changes
  • 1011e33: Select MCP OAuth authorization scopes from WWW-Authenticate challenges or Protected Resource Metadata.

v2.0.31

Patch Changes

v2.0.30

Compare Source

Patch Changes

v2.0.29

Compare Source

Patch Changes

v2.0.28

Compare Source

Patch Changes

v2.0.27

Compare Source

Patch Changes

v2.0.26

Compare Source

Patch Changes

v2.0.25

Compare Source

Patch Changes

v2.0.24

Compare Source

Patch Changes

v2.0.23

Compare Source

Patch Changes

v2.0.22

Compare Source

Patch Changes

v2.0.21

Compare Source

Patch Changes

v2.0.20

Compare Source

Patch Changes

v2.0.19

Compare Source

Patch Changes

v2.0.18

Compare Source

Patch Changes

v2.0.17

Compare Source

Patch Changes

v2.0.16

Compare Source

Patch Changes

v2.0.15

Compare Source

Patch Changes

v2.0.14

Compare Source

Patch Changes
  • 48e7e78: Harden MCP Apps handling of server-supplied resource metadata and the host/iframe bridge:

    • Runtime-validate _meta.ui and drop malformed or non-string fields.
    • Gate iframe permissions deny-by-default via a new sandbox.allowedPermissions allowlist.
    • Derive a concrete postMessage target origin and validate inbound message origins.
    • Validate inbound bridge params: limit resources/read to ui:// resources and allow only https/http/mailto in ui/open-link.
    • Add fingerprintMCPAppResource / detectMCPAppResourceDrift for pinning and comparing app resources.

v2.0.13

Compare Source

Patch Changes

v2.0.12

Compare Source

Patch Changes

v2.0.10

Compare Source

Patch Changes

v2.0.9

Compare Source

Patch Changes

v2.0.8

Compare Source

Patch Changes
  • 3e6e955: Reject in-flight MCP requests when their abort signal fires and remove the pending response handler.
  • eebd14b: Prevent streamable HTTP MCP background SSE disconnects from surfacing as unhandled promise rejections.

v2.0.7

Compare Source

Patch Changes

v2.0.6

Compare Source

Patch Changes

v2.0.5

Compare Source

Patch Changes

v2.0.4

Compare Source

Patch Changes

v2.0.3

Compare Source

Patch Changes

v2.0.2

Compare Source

Patch Changes

v2.0.1

Compare Source

Patch Changes

v2.0.0

Compare Source

Major Changes
  • 23fa161: fix(mcp): setting redirect: error for MCP transport
  • ef992f8: Remove CommonJS exports from all packages. All packages are now ESM-only ("type": "module"). Consumers using require() must switch to ESM import syntax.
  • 8359612: Start v7 pre-release
Patch Changes
  • b79094c: Add resource_link content type to CallToolResultSchema and PromptMessageSchema per MCP spec. Fixes hard rejection when MCP servers return resource_link content parts with zod ≥ 4.4.x.

  • 78e0023: fix(mcp): await addClientAuthentication in token exchange and refresh

  • b567a6c: dependency updates

  • e33ad0b: fix(mcp): add optional hook to validate authorization servers

  • e3ea484: fix(mcp): bypass outputSchema validation when tool returns isError

  • 93afb28: feat(mcp): expose server instructions to be accessible through client

  • a00d1d3: feat(mcp): allow custom fetch for HTTP and SSE transports

  • a98bf66: feat(mcp): surface 'serverInfo' exposed from the MCP server

  • 2a150f8: fix(mcp): lock first sse endpoint received via event

  • 2655da8: fix(mcp): use negotiated protocol version in transport request headers

  • 9f0e36c: trigger release for all packages after provenance setup

  • f7bc0b4: feat(mcp): expose statusCode, url, and responseBody on MCPClientError for HTTP transport failures

    MCPClientError now carries structured HTTP context when it originates from the
    streamable HTTP transport. This lets downstream consumers (e.g. agent frameworks
    that need to decide whether to fall back from streamable HTTP to legacy SSE
    transport per the MCP spec) branch on the actual response status without parsing
    the error message string.

    Fields are optional — they remain undefined for stdio transport errors and for
    non-response failures (network errors, aborts).

  • dcefad3: fix(mcp): respond to ping requests with an empty result per JSON-RPC spec (closes #​6282)

  • b44b051: fix(mcp): prevent prototype-named tools from bypassing the schemas allowlist

    When using client.tools({ schemas }) to expose only an explicitly allowed
    subset of an MCP server's tools, the allowlist check used the in operator,
    which also matches inherited Object.prototype properties. A server-advertised
    tool named constructor, toString, __proto__, etc. would pass the check
    even though the developer never defined it in schemas, and was then exposed to
    the model and executable. The check now uses Object.hasOwn, so only
    explicitly defined tools are returned.

  • f634bac: feat(mcp): add new McpProviderMetadata type

  • b9b3899: changeset for #​13384

  • 1e89d62: fix(mcp): strip trailing slash from OAuth resource parameter

  • 3e0b82f: fix(mcp): support official sdk protocol version negotiation

  • 1451759: feat(mcp): deprecate name and use clientName for MCPClient

  • 7fc6bd6: Raise minimum supported Node.js version to 22. Supported versions: 22, 24, and 26.

  • 08d2129: feat(mcp): propagate the server name through dynamic tool parts

  • 58c9eb1: feat(mcp): add redirect option to MCPTransportConfig for controlling HTTP redirect behavior

  • 0c4c275: trigger initial canary release

  • 611f621: feat(mcp): feat(mcp): add support for MCP Apps

  • 9ecd8ae: fix(mcp): add MCP protocol version 2025-11-25 to supported versions

  • 6c17a9f: fix(mcp): deduplicate auth refresh on http transport

  • 69254e0: feat(ai): add toolMetadata for tool specific metdata

  • 258c093: chore: ensure consistent import handling and avoid import duplicates or cycles

  • f0c6770: fix(mcp): prevent mcp oauth credential exfiltration during rediscovery

  • 5463d0d: feat(provider): align tool result output content file part types with top-level message file part types

  • b8396f0: trigger initial beta release

  • b29e087: fix (mcp): handle SSE messages without explicit event fields

  • 90e2d8a: chore: fix unused vars not being flagged by our lint tooling

  • 024a6b4: fix(mcp): validate oauth metadata issuer during discovery

  • 9b0bc8a: fix(mcp): prevent prototype pollution by using secureJsonParse

  • ff5eba1: feat: roll image-* tool output types into their equivalent file-* types

v1.0.76

Compare Source

Patch Changes

v1.0.75

Compare Source

Patch Changes
  • 878bdb9: Apply MCP scope selection to dynamic client registration as well as authorization.
  • 204ce6c: fix(mcp): reject private OAuth endpoints before sending credentials

v1.0.74

Compare Source

Patch Changes

v1.0.73

Compare Source

Patch Changes

v1.0.72

Compare Source

Patch Changes
  • 0075ed5: fix(mcp): reject SSE requests when POST responses are unsuccessful

v1.0.71

Compare Source

Patch Changes

v1.0.70

Compare Source

Patch Changes

v1.0.69

Compare Source

Patch Changes

v1.0.68

Compare Source

Patch Changes

v1.0.67

Compare Source

Patch Changes

v1.0.66

Compare Source

Patch Changes
  • e8d2654: Honor MCP request deadlines and support bounding or aborting client initialization.

v1.0.65

Compare Source

Patch Changes

v1.0.64

Compare Source

Patch Changes
  • a3bc948: fix(mcp): accept OAuth metadata without code challenge methods

v1.0.63

Compare Source

Patch Changes

v1.0.62

Compare Source

Patch Changes

v1.0.61

Compare Source

Patch Changes

v1.0.60

Compare Source

Patch Changes
  • 937d731: Reject in-flight MCP requests when their abort signal fires and remove the pending response handler.
  • 2b6c67f: Prevent streamable HTTP MCP background SSE disconnects from surfacing as unhandled promise rejections.
  • Updated dependencies [d559de9]

v1.0.59

Compare Source

Patch Changes

v1.0.58

Compare Source

Patch Changes
  • f12f0d3: feat(mcp): expose a json-rpc message validator

v1.0.57

Compare Source

Patch Changes

v1.0.56

Compare Source

Patch Changes

v1.0.55

Compare Source

Patch Changes

v1.0.54

Compare Source

Patch Changes

v1.0.53

Compare Source

Patch Changes

v1.0.52

Compare Source

Patch Changes

v1.0.51

Patch Changes
  • aa39fc8: fix (mcp): handle SSE messages without explicit event fields

v1.0.49

Patch Changes
  • 3e8d9ba: fix(mcp): lock first sse endpoint received via event

  • 4fa7354: fix(mcp): prevent prototype-named tools from bypassing the schemas allowlist

    When using client.tools({ schemas }) to expose only an explicitly allowed
    subset of an MCP server's tools, the allowlist check used the in operator,
    which also matches inherited Object.prototype properties. A server-advertised
    tool named constructor, toString, __proto__, etc. would pass the check
    even though the developer never defined it in schemas, and was then exposed to
    the model and executable. The check now uses Object.hasOwn, so only
    explicitly defined tools are returned.

  • Updated dependencies [bfa5864]

  • Updated dependencies [f42aa79]

v1.0.47

Compare Source

Patch Changes
  • bf1d6bd: fix(mcp): prevent mcp oauth credential exfiltration during rediscovery

v1.0.46

Compare Source

Patch Changes
  • 1f817db: fix(mcp): await addClientAuthentication in token exchange and refresh

v1.0.45

Compare Source

Patch Changes
  • ec5fceb: fix(mcp): respond to ping requests with an empty result per JSON-RPC spec (closes #​6282)

v1.0.44

Compare Source

Patch Changes
  • 77775a4: feat(mcp): expose statusCode, url, and responseBody on MCPClientError for HTTP transport failures

    MCPClientError now carries structured HTTP context when it originates from the
    streamable HTTP transport. This lets downstream consumers (e.g. agent frameworks
    that need to decide whether to fall back from streamable HTTP to legacy SSE
    transport per the MCP spec) branch on the actual response status without parsing
    the error message string.

    Fields are optional — they remain undefined for stdio transport errors and for
    non-response failures (network errors, aborts).

v1.0.43

Compare Source

Patch Changes
  • e2b923f: fix(mcp): deduplicate auth refresh on http transport

v1.0.42

Compare Source

Patch Changes
  • 725f2ed: feat(mcp): expose server instructions to be accessible through client
  • 7281592: fix(mcp): use negotiated protocol version in transport request headers

v1.0.41

Compare Source

Patch Changes

v1.0.40

Compare Source

Patch Changes
  • 221a984: Add resource_link content type to CallToolResultSchema and PromptMessageSchema per MCP spec. Fixes hard rejection when MCP servers return resource_link content parts with zod ≥ 4.4.x.
  • 0084974: feat(mcp): deprecate name and use clientName for MCPClient

v1.0.39

Compare Source

Patch Changes

v1.0.38

Compare Source

Patch Changes

v1.0.37

Compare Source

Patch Changes

v1.0.36

Patch Changes
  • 9a8d276: feat(mcp): surface 'serverInfo' exposed from the MCP server

See associated pull request for more information.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant