About Dynamic Tool MCP Server
Dynamic Tool MCP Server is an MCP server published by scitara-cto in the Developer Tools category: a basic MCP server using the SSE transport that can be used to test dynamic tool creation/management. It has been installed 0 times through Conduid.
The repository has 2 stars and 1 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.
Install
npx dynamic-tool-mcp-serverThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Dynamic Tool MCP Server
Powered by Claude · Grounded in docs
Security checks
- ·README presentNot checked yet.
- ·License declaredNot checked yet.
- ·Tests presentNot checked yet.
- ·Dependencies pinnedNot checked yet.
- ·No dynamic code executionNot checked yet.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
README
Dynamic Tool MCP Server
This is a basic MCP (Model Control Protocol) server implementation designed for testing MCP clients. The server demonstrates dynamic tool management capabilities, allowing tools to be added at runtime.
Features
The server comes with two built-in tools:
-
Hello Tool (
hello)- A simple greeting tool that takes a name parameter
- Returns a greeting message
- Example:
hello("World")returns "Hello, World!"
-
Add Tool Tool (
add_tool)- Dynamically adds new tools to the MCP server
- Takes a tool name and description as parameters
- After adding a tool, notifies connected MCP clients about the tool list change
- Clients should respond by requesting an updated tool list
Dynamic Tool Management
The server implements the MCP protocol's dynamic tool management feature. When a new tool is added using the add_tool tool:
- The tool is registered with the server
- The server sends a notification to all connected clients about the tool list change
- Clients should respond by requesting an updated tool list
- The new tool becomes immediately available for use
This functionality makes this server ideal for testing MCP client implementations, particularly their ability to:
- Handle dynamic tool list updates
- Request and process updated tool lists
- Support runtime tool registration
Getting Started
-
Install dependencies:
npm install -
Start the server:
npm start
The server will run on http://localhost:4100 by default.
Configuration
The server can be configured through the .cursor/mcp.json file:
{
"mcpServers": {
"dynamic-tool": {
"url": "http://localhost:4100/sse"
}
}
}
Testing
This server is particularly useful for testing MCP client implementations that need to handle dynamic tool management. It allows you to verify that your client:
- Correctly processes tool list change notifications
- Properly requests and handles updated tool lists
- Can use newly added tools immediately after they're registered
README mirrored from the source repository 3 months ago. The original is authoritative.