openclaw - 💡(How to fix) Fix [Feature]: Feature Request: Support tool alias/renaming for MCP servers to avoid name conflicts [1 participants]

Fix Plan

To support tool aliasing/renaming in the MCP server configuration, follow these steps:

• Update the MCP server configuration to include a toolAlias or toolPrefix property.
• For the toolAlias approach:
  • Add a toolAlias object to the server configuration.
  • Specify the original tool name as the key and the desired alias as the value.
• For the toolPrefix approach:
  • Add a toolPrefix property to the server configuration.
  • Specify the desired prefix for the tool names.

Example configuration using toolAlias:

{
  "mcp": {
    "servers": {
      "minimax": {
        "command": "uvx",
        "args": ["minimax-coding-plan-mcp", "-y"],
        "env": {
          "MINIMAX_API_KEY": "...",
          "MINIMAX_API_HOST": "https://api.minimax.io"
        },
        "toolAlias": {
          "web_search": "minimax_web_search",
          "understand_image": "minimax_understand_image"
        }
      }
    }
  }
}

Example configuration using toolPrefix:

{
  "mcp": {
    "servers": {
      "minimax": {
        "command": "uvx",
        "args": ["minimax-coding-plan-mcp", "-y"],
        "toolPrefix": "minimax_"
      }
    }
  }
}

Verification

To verify that the fix worked, check that:

• The MCP server is able to register tools with the aliased or prefixed names.
• The user is able to access the tools with the aliased or prefixed names without conflicts.

Extra Tips

• Make sure to update the MCP server configuration correctly to avoid any syntax errors.
• Test the configuration with different tool names and prefixes to ensure that the aliasing/renaming works as expected.