Cliff Hall

From the discussion in the [contributor's Discord](https://discord.com/channels/1358869848138059966/1438040410197856286) There's a reason for the validation. The protocol defines the message types. Clients and servers are usually written by separate entities, and so...

> So now the PR just supports client-side handlers for the expected notification types defined in the protocol. @kylestratis You should probably tidy the language in the PR description to...

We have [model hints](https://modelcontextprotocol.io/specification/2025-06-18/client/sampling#model-hints) in the sampling section of the spec. Expanding that approach to other corners of the spec where it would be useful seems right. But I don't...

In https://github.com/modelcontextprotocol/inspector/pull/284 we did eliminate the form for complex objects because it was not always possible to render the form correctly, nor was it possible to detect when it could...

> In the inspector I'm seeing errors about missing input even when the inputs are optional (i.e., omitted from the `required` array on the input schema): I'm not certain this...

Hi @ln-12! Thanks for the ping on this. I've reopened #434 (see [my comment](https://github.com/modelcontextprotocol/inspector/pull/434#issuecomment-3165685567)).

> @cliffhall updated the readme. Feel free to reword Looks good, I'm testing now. Needs an `npm run prettier-fix` to pass CI.

Hey @localden. Can you provide an example server and steps to repro?

Fixed in #345

> In case it's useful at all, I've got a demo MCP server that returns 401/www-authenticate [here](https://github.com/clerk/mcp-nextjs-example)! I have tested this with a client that handles auth properly according to...