Dynamic Tool MCP Server

What is Dynamic Tool MCP Server?

A basic MCP (Model Control Protocol) server implementation designed for testing MCP clients. It demonstrates dynamic tool management capabilities, allowing tools to be added at runtime. Intended for developers testing MCP client implementations.

How to use Dynamic Tool MCP Server?

Install dependencies with npm install, then start the server with npm start. The server runs on http://localhost:4100 by default. Configure clients via .cursor/mcp.json by pointing to http://localhost:4100/sse. Use the built-in hello tool for greeting and add_tool to dynamically register new tools at runtime.

Key features of Dynamic Tool MCP Server

• Two built-in tools: hello and add_tool
• Dynamic tool registration at runtime
• Sends tool list change notifications to connected clients
• Clients can request updated tool lists after changes
• New tools become immediately available after addition
• Designed for testing MCP client dynamic tool handling

Use cases of Dynamic Tool MCP Server

• Testing MCP client ability to process tool list change notifications
• Verifying client requests and handles updated tool lists correctly
• Testing immediate usability of dynamically added tools

FAQ from Dynamic Tool MCP Server

What is the difference between the hello and add_tool tools?

hello takes a name parameter and returns a greeting. add_tool takes a tool name and description, registers a new tool, and notifies clients of the change.

What runtime dependencies are required?

Node.js and npm are required. Dependencies are installed via npm install.

On which transport does the server run?

The server uses SSE transport at http://localhost:4100/sse.

Can tools be removed after being added?

The README does not mention tool removal; only dynamic addition is described.

Is authentication or authorization supported?

—