The library handles generating all the MCP endpoints and input schemas for the model by introspecting the types of the structs + annotations for the handlers.
I'm currently working on filling out the rest of the optional server features in the protocol and hope to move on to a client implementation soon. If any folks find this interesting, help is always appreciated!
Something that I don’t get about MCP servers is how will this work in Production when the MCP server is used by many clients. It does not have auth built in. Does this mean that users will have to host their own MCP Servers locally? It’s just not very practical.
I know it’s not related to your Go SDK, it’s just something that I have been wondering.
And there's a concrete PR open at https://github.com/modelcontextprotocol/specification/pull/1... which suggests that there will be an auth capability with both oauth and credential (api keys etc) which seems like it will make it's way into the next release of the spec
I know it’s not related to your Go SDK, it’s just something that I have been wondering.