mcpField
D
Dynamic Tool MCP Server

Dynamic Tool MCP Server

Remote
github.com/scitara-ctoDeveloper Tools2Updated 78w ago
Repository

About Dynamic Tool MCP Server

Dynamic Tool MCP Server is an SSE-based server for testing MCP clients. Its built-in tools let clients exercise runtime tool registration and tool-list change notifications.

Key features

  1. 01SSE transport
  2. 02Greeting tool
  3. 03Add tools at runtime
  4. 04Notify clients of tool-list changes

Use cases

  1. 01Test client handling of tool-list updates
  2. 02Verify newly registered tools are usable

MCP support

An MCP server using SSE that exposes `hello` and `add_tool`. Adding a tool notifies connected clients so they can retrieve the updated tool list.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttp://localhost:4100/sse
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project 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:

  1. Hello Tool (hello)

    • A simple greeting tool that takes a name parameter
    • Returns a greeting message
    • Example: hello("World") returns "Hello, World!"
  2. 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:

  1. The tool is registered with the server
  2. The server sends a notification to all connected clients about the tool list change
  3. Clients should respond by requesting an updated tool list
  4. 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

  1. Install dependencies:

    npm install
    
  2. 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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.