Repository navigation
Package attaches process signal handlers #817
Description
Describe the bug
Installing the @modelcontextprotocol/sdk package will include examples, which add signal handlers to process of application.
To Reproduce
Steps to reproduce the behavior:
- Install version
1.16.0of@modelcontextprotocol/sdk - Examine installed node_module folder (
node_modules/@modelcontextprotocol/sdk/dist/esm/examples) - Notice that examples are loaded due to exports declaration
Expected behavior
Examples should not be included in production distribution and signal handlers should not be attached
Logs
If applicable, add logs to help explain your problem.
Additional context
This causes some downstream plugins (like our webserver signal processor) to have issues. Seems like these were included unintentionally during the packaging process.
Activity
MustafaKemal0146 commentedon Jul 16, 2026
Hi, I verified this against the current
v1.xbranch. The v2mainlayout no longer has this packaging path, but bothtsconfig.prod.jsonandtsconfig.cjs.jsononv1.xstill compilesrc/examples/**intodist, and the wildcard package export makes those example entry points importable. Importing a server example can then attach process signal handlers as a module side effect.I can submit a focused
v1.xfix that excludessrc/examples/**from both production builds, with regression coverage that inspects the packed artifact to ensure example entry points are absent while supported SDK subpaths remain available. I also found no open or draft PR implementing this packaging change. Is this available for community contribution, and may I be assigned before starting implementation?