fix: rename core to spec #8
Conversation
This is to clarify the separation of concerns. It also helps avoid a name conflict on crates.io
|
I run the mcp-core crate and was wondering if we could collaborate and solve this issue so this could be the official mcp-core |
|
Somewhat related, I mentioned in #17 using generated bindings from the official spec's JSON schema rather than the current hand-rolled types. I've published a simple version at https://crates.io/crates/mcp-types, if there is interest, happy to remove so the name can be used. mcp-spec is nice too. |
|
@baxen I'm the author of that crate and I don't mind changing it as long as all of these crates will be live on crates.io and this project is production ready as I currently run remote SSE mcp servers with my crate. |
|
@stevohuncho Hey! Thank you so much for reaching out and sorry for my slow reply, i've been offline last week. We're looking to bring everyone building these together into this space, and would be very enthusiastic for you to come contribute here. Can you please hop into #29 - i'd like to kick off the discussion of combining what we all have got into this space there. We probably have a little up front work to pick between some interface choices and then let's get this into a stable release |
|
given this discussion i'm going to hold off merging this PR |
Renaming core to spec to clarify organization (#6) and to avoid naming conflicts on crates.io