modelcontextprotocol / modelcontextprotocol/typescript-sdk
Dynamic MCP Tool Registration Not Available Mid-Chain or Same Cycle
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.4k
- Forks
- 2.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 4
Description
I have the problem, I'm trying to configure a dynamic MCP server with dynamic tools. Dynamic tool registration works on the server and is reflected in the client tools UI, but the tool is not discoverable or invokable during the same message cycle or in the middle of a chain. It only becomes available after the current chain finishes execution.
what can be possible fix for this ?
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 reproducing dynamic tool registration during a message cycle and trace when the client refreshes its available tools. Done means a tool registered mid-chain is discoverable and invokable before the current chain finishes, with the existing behavior covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100