Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Further split of this library into modules (e.g. api, client, server) #33

Open
morisil opened this issue Jan 7, 2025 · 1 comment
Open

Further split of this library into modules (e.g. api, client, server) #33

morisil opened this issue Jan 7, 2025 · 1 comment
Labels
enhancement New feature or request

Comments

@morisil
Copy link
Contributor

morisil commented Jan 7, 2025

Is your feature request related to a problem? Please describe.
I want to use some of the MCP defined types as data transfer objects received in the kotlin multiplatform project with js targets. In general my clients don't care about the server transport part. The current structure of this projects forces me to also depend on server compontens from ktor.

Describe the solution you'd like
This project can be split into multimodule multiplatform project, where types API is kept as a separate module.

Describe alternatives you've considered
I guess an alternative would be dependency exclusions.
@morisil morisil added the enhancement New feature or request label Jan 7, 2025
@morisil
Copy link
Contributor Author

morisil commented Jan 7, 2025

BTW I would be happy to contribute a PR for this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@morisil