modelcontextprotocol / modelcontextprotocol/typescript-sdk
creation of a tool without any server instance knowledge
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.4k
- Forks
- 2.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 4
Description
For now we can only create a tool with server.registerTool(name, options, callback)
I means to create one tool I'm force to have already create the server an to have its instance
In opposite, in Langchain management, you create tools with import {tool} from '@langchain/core/tools'; function and create the tool anywhere,
Then you associate it with the graph / llm you want
The advantage of the Langchain management is I can for example create a library of tools, then in another package, create a server and associate the tools to it.
Here I cannot. Or I miss something in the documentation ?
Is there's any way to construct a tool outside of a mcpServer instance ?
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 reading the current server.registerTool(name, options, callback) API and the SDK documentation around tool creation. Compare that flow with the requested standalone tool construction and later association with a server, using the LangChain example in the issue as context. Done means the supported design or limitation is documented and, if supported, a tool can be created without an MCP server instance and then associated with one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100