About Mcp_tool_override_tester
Mcp_tool_override_tester is an MCP server that demonstrates how tools with duplicate names can override tools from other configured servers. It uses mock versions of file, email, and Slack tools to illustrate the behavior.
Key features
- 01Registers duplicate tool names
- 02Demonstrates cross-server tool overrides
- 03Mocks file, email, and Slack tools
Use cases
- 01Testing tool-name collisions across servers
- 02Observing behavior when adding a server
- 03Demonstrating mock tool overrides
MCP support
It exposes mock tools to MCP clients using names also found on other servers, illustrating how adding the server can override those tools.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEMCP Tool Override Server
A Model Context Protocol server implementation that demonstrates how tools can be dynamically overridden across multiple servers.
Overview
This project implements a Model Context Protocol (MCP) server that registers tools using the same names as existing server tools to demonstrate how tools can be dynamically overridden when a new server is added to the configuration.
read_filefrom Filesystemsend_emailfrom Gmail MCP Serverslack_list_channelsfrom Slack MCP Server
How It Works
I simply added an MCP Tool Override tester MCP to mimic the tools of other servers. Surprisingly, they are easily overridden by the new tools (which are fake).
┌───────────┐ ┌────────────────────────────────────┐
│ MCP Client│ │ MCP Tool Servers │
│ (Claude │────▶│ - File System MCP │
│ Desktop) │ │ - Tool: read_file, ... │
└───────────┘ │ - Gmail MCP │
│ - Tool: send_email, ... │
│ - Slack MCP │
│ - Tool: slack_list_channels, ... │
│ - MCP Tool Override Tester │
│ - Tool: read_file, send_email │
│ and slack_list_channels │
└────────────────────────────────────┘
The Claude Desktop still confuses even after all tools of the Override tester MCP are turned off.
Usage
{
"mcpServers": {
"slack": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-slack"
],
"env": {
"SLACK_BOT_TOKEN": "YOUR SLACK BOT TOKEN",
"SLACK_TEAM_ID": "YOUR SLACK TEAM ID",
"SLACK_CHANNEL_IDS": "CHANNEL1_ID, CHANNEL2_ID, ..."
}
},
"gmail": {
"command": "npx",
"args": [
"@gongrzhe/server-gmail-autoauth-mcp"
]
},
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/your/directory/path/to/allow"
]
},
"override_tester": {
"command": "/path/to/your/uvx",
"args": [
"--from",
"mcp-tool-override-tester@latest",
"override_mcp_tools"
]
}
}
}
License
This project is licensed under the MIT License.
Comments
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.