You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
One issue with the current package setup is it's difficult for them to be used as a NPM package, as they're made for "CLI-setup".
Describe the solution you'd like
Refactor all the servers so they export a function that instantiates the server parameters for in-memory usage. Every server should export in its index file:
You can still have a bin/cli.ts entry-point, but simultaneously allow dual use as a plain node module.
Describe alternatives you've considered
We could keep it as it is but it'll require spawning node servers for each server. It might not be a clean pattern if we are to use these MCPs within custom agent designs.
Open to suggestions though!
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
One issue with the current package setup is it's difficult for them to be used as a NPM package, as they're made for "CLI-setup".
Describe the solution you'd like
Refactor all the servers so they export a function that instantiates the server parameters for in-memory usage. Every server should export in its index file:
This is sort of what I'm trying to do here (https://github.com/unroute/typescript-sdk), but would be great if the official package sets this as an example.
You can still have a
bin/cli.ts
entry-point, but simultaneously allow dual use as a plain node module.Describe alternatives you've considered
We could keep it as it is but it'll require spawning node servers for each server. It might not be a clean pattern if we are to use these MCPs within custom agent designs.
Open to suggestions though!
The text was updated successfully, but these errors were encountered: