David Soria Parra
David Soria Parra
I am not sure I fully understand. MCP is a client / server architecture. Clients and Servers operate independently and speak over a transport to each other. # Implementing a...
Webhooks are HTTP based. This leaks the transport layer into the data layer of the protocol and wouldn't work in a stdio case. I think there is use in a...
I am closing this for no. If we feel this should exists, then let's create a SEP.
I think having examples would actually be good, but we should probably choose examples that were implemented.
Should we do this and deprecate the old module?
I agree, this is a typo. The problem is that we a lot of existing code (see https://github.com/search?q=mcp+AND+-32002&type=code) that uses `-32002`. If we were to change this, clients and servers...
This is an early draft. Happy to bikeshed the exact schema format. I am very much not tied to the specific format. Open to suggestions.
> Everyone involved with Registry has been calling this concept `server.json` (vs. `MCP Server Card`). While I would have a slight preference to continue calling it `server.json`, I don't feel...
> > MCP servers supporting HTTP-based transports (including Streamable HTTP and SSE) SHOULD provide a server card via a .well-known URI. > > Why not "MUST"? Feels like this could...