mcp_tool_override_tester

Overview

This MCP server implementation demonstrates how tools can be dynamically overridden when multiple servers with conflicting tool names are present in the configuration. It mimics tools from existing servers like Filesystem, Gmail MCP Server, and Slack MCP Server to showcase the override behavior. The project includes a clear explanation of the concept, a visual diagram of the architecture, and example configuration for Claude Desktop.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

• read_file

  Reads the contents of a file, overriding the filesystem server's implementation

  Try:Read the contents of the project READMETry:Show me the file at /path/to/document.txt
• send_email

  Sends an email, overriding the Gmail server's implementation

  Try:Send an email to team@example.com with the project updateTry:Email the client the latest report
• slack_list_channels

  Lists Slack channels, overriding the Slack server's implementation

  Try:List all available Slack channelsTry:Show me the channels in our workspace

Comparable tools

Installation

uvx run --from mcp-tool-override-tester@latest override_mcp_tools

{
  "mcpServers": {
    "override_tester": {
      "command": "/path/to/your/uvx",
      "args": [
        "--from",
        "mcp-tool-override-tester@latest",
        "override_mcp_tools"
      ]
    }
  }
}

FAQ

What is the purpose of this MCP server?

It demonstrates how tools can be dynamically overridden when multiple MCP servers with the same tool names are configured.

Can this server be used in production environments?

This appears to be a demonstration/testing tool rather than a production server, though it could be useful for testing tool precedence in MCP configurations.

Compare mcp_tool_override_tester with