anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-23 02:36:57 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]: MCP tool renaming #7381

New Issue
Open
opened 2026-02-16 18:07:00 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:07:00 -05:00
Owner
Copy Link
Copy Source

Originally created by @Jaid on GitHub (Jan 23, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

The automatically chosen tool names are sometimes confusing, unnecessarily long or arbitrary.

For example, these are the names of the tools I get when only the Brave Search MCP server is enabled:

Session screenshot

The duplication of the brand prefix wastes tokens and UI space.

I would like to be able to permanently rename the “brave_brave_web_search” to “brave_web_search” or, even better, just “web_search” to also abstract away the explicit backend used (which should not concern the clanker).

This could be implemented by extending the configuration schema, like:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "brave": {
      "enabled": true,
      "type": "remote",
      "url": "http://brave-search.local",
      "tools": {
        "brave_web_search": {
          "rename": "web_search"
        }
      }
    }
  }
}

Or more abstract to keep the possibility to overwrite other fields in the future:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "brave": {
      "enabled": true,
      "type": "remote",
      "url": "http://brave-search.local",
      "tools": {
        "brave_web_search": {
          "overlay": {
            "name": "web_search"
          }
        }
      }
    }
  }
}

Spec details:

  • Renaming should suppress the automatic concatenation of the server name and tool name. The name chosen in the config should be final.
  • If the clanker chooses to call a tool by its original name instead of the user-defined one, it should be treated as a legal alias.

I can also make a pull request for this if wanted.

Originally created by @Jaid on GitHub (Jan 23, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request The automatically chosen tool names are sometimes confusing, unnecessarily long or arbitrary. For example, these are the names of the tools I get when only the [Brave Search MCP server](https://www.npmjs.com/package/@brave/brave-search-mcp-server) is enabled: - https://opncd.ai/share/H9maRLf3 <a href="https://opncd.ai/share/H9maRLf3"><img alt="Session screenshot" src="https://github.com/user-attachments/assets/8c13bc43-12d5-43c3-8c2d-898eb9296498" /></a> The duplication of the brand prefix wastes tokens and UI space. I would like to be able to permanently rename the “brave_brave_web_search” to “brave_web_search” or, even better, just “web_search” to also abstract away the explicit backend used (which should not concern the clanker). This could be implemented by extending the configuration schema, like: ```jsonc { "$schema": "https://opencode.ai/config.json", "mcp": { "brave": { "enabled": true, "type": "remote", "url": "http://brave-search.local", "tools": { "brave_web_search": { "rename": "web_search" } } } } } ``` Or more abstract to keep the possibility to overwrite other fields in the future: ```jsonc { "$schema": "https://opencode.ai/config.json", "mcp": { "brave": { "enabled": true, "type": "remote", "url": "http://brave-search.local", "tools": { "brave_web_search": { "overlay": { "name": "web_search" } } } } } } ``` Spec details: - Renaming should suppress the automatic concatenation of the server name and tool name. The name chosen in the config should be final. - If the clanker chooses to call a tool by its original name instead of the user-defined one, it should be treated as a legal alias. --- I can also make a pull request for this if wanted.
yindo added the discussion label 2026-02-16 18:07:00 -05:00
yindo commented 2026-02-16 18:07:00 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 23, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #7399: Filter which tools are loaded from MCP servers (includeTools/excludeTools) - Related to MCP tool management
  • #3523: Tool names too long (exceeding 64-character limit) - This is a related bug where concatenating server name + tool name creates problems

#3523 specifically highlights the issue you're experiencing with tool name concatenation causing the 'brave_brave_web_search' duplication and length problems.

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 23, 2026): This issue might be a duplicate of existing issues. Please check: - #7399: Filter which tools are loaded from MCP servers (includeTools/excludeTools) - Related to MCP tool management - #3523: Tool names too long (exceeding 64-character limit) - This is a related bug where concatenating server name + tool name creates problems #3523 specifically highlights the issue you're experiencing with tool name concatenation causing the 'brave_brave_web_search' duplication and length problems. Feel free to ignore if none of these address your specific case.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7381
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?