MCP.so
ログイン

MCP Tool Override Tester

@kibitzing

基本情報

カテゴリ

その他

トランスポート

stdio

作者

kibitzing

MCP Tool Override Tester について

A Model Context Protocol server implementation that demonstrates how tools can be dynamically overridden across multiple servers.

MCP Tool Override Tester の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

MCP Tool Override Tester のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is Mcp_tool_override_tester?

Mcp_tool_override_tester is a demonstration MCP server that registers tools with the same names as tools from other servers (Filesystem, Gmail, Slack) to show how tools are dynamically overridden when a new server is added. It is intended for developers who want to understand tool conflict and override behavior in MCP configurations.

How to use Mcp_tool_override_tester?

Add the server to your MCP configuration (e.g., Claude Desktop’s mcpServers) using the provided JSON snippet. Use uvx to run the package mcp-tool-override-tester@latest with the command override_mcp_tools. No additional environment variables or credentials are required, as the tools are fake.

Key features of Mcp_tool_override_tester

  • Demonstrates tool name collision and override behavior.
  • Mimics tools from Filesystem, Gmail, and Slack servers.
  • Requires no real credentials or external services.
  • Easy to add to any existing MCP configuration.

Use cases of Mcp_tool_override_tester

  • Testing how MCP clients handle tool name conflicts.
  • Experimenting with tool override priority when adding new servers.
  • Understanding the behavior of Claude Desktop with conflicting tool names.
  • Debugging configuration issues caused by tool name clashes.

よくある質問

1

What does this server do?

It registers tools (`read_file`, `send_email`, `slack_list_channels`) with the same names as tools from other MCP servers to demonstrate how the client resolves name conflicts when a new server is added.

2

How are tools overridden?

When a new server is added to the configuration, its tools automatically override any existing tools with the same name. The override is easy to achieve, even with fake (non-functional) tools.

3

Does this server affect real tools even after being turned off?

Yes. The README notes that Claude Desktop still confuses tools even after all tools of the override tester are turned off.

4

What tools does it mimic?

It mimics `read_file` (from the Filesystem server), `send_email` (from the Gmail MCP server), and `slack_list_channels` (from the Slack MCP server).

5

Is this server intended for production use?

No. It is a demonstration and testing tool for understanding tool override mechanics, not a functional replacement for the real servers.

コメント

「その他」の他のコンテンツ