Repository navigation
Split the core from the server and client implementations #2486
Description
Activity
I think we can have a
mcp-slimor something like that yes.mcp-coreis taken.I think we can have
serverandclientextra groups. Or...?My real use case is to have a server that does not depend on starlete (as I wanna inject it into a django with wsgi and reuse my auth).
Reacted by tiyujopiteThanks for the report. Tracking this in #3 instead. Closing as part of a general backlog cleanup ahead of the v2 release. If this is still relevant against current
main, feel free to reopen.Its not the same
Description
In the current way of shipping the lib, it carries many deps, and many of them are never used in some integrations. For instance django-mcp-server does not need another http server. Also if one is doing a server httpx is not required.
My proposal is to either make those deps optional, or split out a
mcp-corelib that does not carry this deps.References
No response