dynamic-tool
A basic MCP server using the SSE transport that can be used to test dynamic tool creation/management
claude mcp add --transport stdio scitara-cto-dynamic-tool-mcp-server node server.js
How to use
Dynamic Tool MCP Server is a testing-oriented MCP server that demonstrates runtime tool management. It ships with two built-in tools: a Hello tool that greets a given name, and an Add Tool tool that dynamically registers new tools at runtime. When you call add_tool with a new tool name and description, the server registers the tool and broadcasts a notification about the updated tool list to all connected clients. Clients should then request the updated tool list and can immediately start using the newly added tool. This setup is ideal for validating MCP clients’ ability to handle dynamic tool list updates and immediate tool availability.
To interact with the server, connect as an MCP client, use the Hello tool by invoking hello("Name") to get a greeting, and experiment with add_tool to extend the tool set. After adding tools, listen for the server’s tool-list-change notifications and refresh your tool list accordingly to discover and utilize the new capabilities in real time.
How to install
Prerequisites:
- Node.js (14.x or newer)
- Internet access to install dependencies
-
Clone or download the repository:
- git clone <repository-url>
- cd <repository-directory>
-
Install dependencies:
- npm install
-
Start the server:
- npm start
-
Verify the server is running:
- Open a browser or HTTP client to http://localhost:4100
- Use an MCP client to connect and begin interacting with the tool list
If you prefer a direct command instead of npm scripts, you can run the server with Node directly (assuming server.js is the entry point):
- npm run build-if-needed (if the project exposes a build step)
- node server.js
Additional notes
Tips and common considerations:
- The server runs by default at http://localhost:4100. If you need to change the port, adjust the server configuration or environment variables as appropriate for your setup.
- Dynamic tool registration is broadcast to all connected clients. Clients should respond by requesting an updated tool list to discover and use the new tool immediately.
- The built-in Hello tool expects a name parameter, e.g., hello("World"). The Add Tool tool requires a tool name and a description, which becomes visible in the tool list for subsequent requests.
- If you encounter connection issues, ensure the MCP client targets the correct URL and that any required CORS or network permissions are configured for your environment.
- For troubleshooting, inspect server logs to confirm that add_tool is registering the new tool and that the tool list change notification is emitted.
Related MCP Servers
zen
Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage
MCP -Deepseek_R1
A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)
mcp-fhir
A Model Context Protocol implementation for FHIR
mcp
Inkdrop Model Context Protocol Server
mcp-appium-gestures
This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..
dubco -npm
The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.