modelcontextprotocol / modelcontextprotocol/typescript-sdk
Simplify public access to McpServer registered tools
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.
Sometimes it's more suitable to do some post-registration processing for tools than do so right away or store references to RegisteredTool[] elsewhere.
For that, It would be great to have some method/getter to get all current registered tools
Describe the solution you'd like
2 options:
- method:
getAllRegisteredTools()=>RegisteredTool[] - getter:
registeredTools=>RegisteredTool[]
Describe alternatives you've considered
It can return the same type as it's now in _registeredTools
Additional context
Here is the PR where half of changes can be replaced just by one cycle at the end of all tools registration: https://github.com/microsoft/azure-devops-mcp/pull/604
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 in src/server/mcp.ts at the _registeredTools definition referenced in the issue, and inspect how McpServer registration currently exposes or stores tools. Add a public method or getter that returns the current RegisteredTool[] collection, then verify that callers can access all tools after registration and run the relevant existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 67/100