softwaremill / softwaremill/chimp
Adding/removing endpoints on runtime
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 102
- Forks
- 10
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 16
Description
Hi!
That's a really cool library!
I have a question/feature request, but I'm not sure how this should be done, as I'm not familiar with tapir's internals.
- Servers can notify clients when tools change using notifications/tools/list_changed
- Tools can be added or removed during runtime
Is this already possible in chimp?
It's the first time for me using tapir, so I'm not sure if it's possible to, for example, make a tapir endpoint, pass it to a Pekko interpreter, and then update the endpoint on runtime.
The other component of this would be the notifications mentioned by the spec.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names tapir endpoints, the Pekko interpreter, and MCP tool-discovery notifications, but no repository files or tests. Start by locating the endpoint-to-interpreter integration and reviewing the referenced MCP specification; done would require a decided approach for runtime tool changes and the associated client notification behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100