-
Notifications
You must be signed in to change notification settings - Fork 4k
Split the core from the server and client implementations #2486
Copy link
Copy link
Open
Labels
P3Nice to haves, rare edge casesNice to haves, rare edge casesenhancementRequest for a new feature that's not currently supportedRequest for a new feature that's not currently supportedneeds decisionIssue is actionable, needs maintainer decision on whether to implementIssue is actionable, needs maintainer decision on whether to implementv2Affects the v2 line (2.x on main)Affects the v2 line (2.x on main)
Description
Activity
Metadata
Metadata
Assignees
Labels
P3Nice to haves, rare edge casesNice to haves, rare edge casesenhancementRequest for a new feature that's not currently supportedRequest for a new feature that's not currently supportedneeds decisionIssue is actionable, needs maintainer decision on whether to implementIssue is actionable, needs maintainer decision on whether to implementv2Affects the v2 line (2.x on main)Affects the v2 line (2.x on main)
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