feat: add url property to RequestInfo interface

[valentinbeggi]

Summary

• Add optional url property to RequestInfo interface exposing the request URL
• Enables server handlers to access query parameters and path info from incoming requests

Closes #1351

export interface RequestInfo {
    headers: IsomorphicHeaders;
    url?: string;  // e.g., "http://localhost:3000/mcp?foo=bar" or "/?sessionId=abc"
}

Note: Could type url as URL instead of string for better DX (.searchParams, .pathname, etc). However, Node.js IncomingMessage.url is a relative path (/path?query), requiring a base URL to construct. Happy to implement if preferred.

Test plan

• Updated existing requestInfo tests to verify url property

[changeset-bot]

🦋 Changeset detected

Latest commit: b8cb152

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/sdk@1353

commit: b8cb152

[mattzcarey]

Unfortunately the node server req.url only gives the path not the base url. The web standards request.url gives the full url. atm this will have inconsistent behaviour across the different transports.

cc. @KKonstantinov

EDIT: i read the comment fully. I think I would prefer URL type and unify it across transports.

[valentinbeggi]

@mattzcarey updated ✅

[paulleseute]

@mattzcarey Can we please merge this ? This is much needed now Claude requires the resources meta to embed an hash of the path as domain (MCP server can be served on multiple endpoints).

[mattzcarey]

This is coming in v2 but maybe we should back port @felixweinberger ?