Auto-generated MCP types from JSON schema

[cbrit]

I had published an early-development mcp-types crate for types generated directly from the 11-05-24 specification schema using typify, as it seems valuable to have a crate that represents auto-generated bindings directly from each new spec as they are released rather than having to manually create them or tell a GPT to.

I was also in the middle of implementing its use in the offeryn crate(s) when this repo was released.

One important issue I was working through is the schema that allow additionalProperties fields don't generate a field to represent them, and only result in types with a meta field in the params. I was trying to solve this by editing the AST directly after generation.

Anyway, is there interest in merging that effort somehow?

[baxen]

Yes this sounds great! Let's make sure we coordinate with #29 and any other consolidation. This might make our need for an "mcp-spec" unecessary and we'd be happy to remove it