modelcontextprotocol / modelcontextprotocol/typescript-sdk
Elicitation with custom input [ SEP-1456 ]
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.4k
- Forks
- 2.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 4
Description
Is your feature request related to a problem? Please describe.
I want the elicitation to show some pre-defined input options, but want to give flexibility that user could input a custom string as well.
Describe the solution you'd like
It would be ideal if there's an option/flag to allow custom input even when enum of predefined values is provided
Describe alternatives you've considered
Currently chaining the elicitation requests is the only way.
1st elicitation request has predefined options with an additional option named "Other".
2nd elicitation request would then allow custom string input.
Additional context
Chaining of elicitation often causes subsequent elicitations to timeout within 2-3 seconds and it does not seem to follow the default timeout of 60 seconds. I have mentioned a bug here: #903 — and its observed by others as well.
Contributor guide
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
Start by tracing the TypeScript SDK's elicitation request handling and how predefined enum options are represented. Check the related timeout issue #903 for context; done means an elicitation can offer predefined options while accepting a custom string without chaining requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100