Jonathan Hefner
Jonathan Hefner
> The problem is that we a lot of existing code (see https://github.com/search?q=mcp+AND+-32002&type=code) that uses `-32002`. It's worth pointing out that "-32002" is not resource-related in some of those results....
Rather than `type`, perhaps `category`? Then servers could automatically be placed in zero or more categories (e.g., `["remote", "sse", "streamable-http"]`). And we could add arbitrary categories in the future. Though...
> did you see my suggestion of `filter` instead of `type`? Curious what you think of `filter`. > I don't love category personally, because category is typically a mutually exclusive...
If the `server.json` format eventually becomes used for non-registry purposes, it seems likely that the schema source of truth would be moved to the `modelcontextprotocol/modelcontextprotocol` repo. In which case, the...
> This SEP proposes adding a standardized discovery mechanism for HTTP-based MCP servers using a `.well-known/mcp.json` endpoint. This enables clients to automatically discover server capabilities, available transports, authentication requirements, protocol...
> One limitation discussed in [this comment](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/383#issuecomment-2911300705) (which we independently arrived at as well) is that notifications may be ignored by clients, requiring a full result to be sent at...
> Wouldn't the `progressToken` be sufficient? I know not the most elegant solution. In my opinion, progress notifications and partial results are orthogonal features. Also, progress notifications are optional, so...
> How does the client know to append to the previous content or create a new one element. From https://github.com/modelcontextprotocol/modelcontextprotocol/pull/776#issuecomment-2985254656: "One approach would be to include something like `_meta.mergeStrategy` in...
@mpcm Sorry for the ping, but since you weighed on #414, I was wondering if you could weigh in here also. :pray: For JSON-RPC, when sending partial results to the...
One field that I would really like to include (though it will likely have to be optional) is a dedicated URL pointing to server installation instructions (i.e., documentation for how...