Add complete Serena MCP tool name mappings

[Copilot]

src/toolNames.json only had 2 of Serena's ~40 MCP tools mapped (activate_project, get_current_config), causing all other Serena tool invocations to show as unknown in the Usage Analysis dashboard.

Changes

• src/toolNames.json: Added all 38 missing Serena tool entries in mcp_oraios_serena_<tool_name> → "Serena: <Tool Name>" format, grouped with existing Serena entries. Source: oraios/serena official tool list.

Coverage now includes core file/symbol operations (find_symbol, replace_symbol_body, search_for_pattern, rename_symbol), memory tools (read_memory, write_memory, list_memories), project management (onboarding, remove_project, activate_project), JetBrains-backend variants (jet_brains_find_symbol, jet_brains_type_hierarchy, etc.), and thinking/workflow tools (think_about_task_adherence, summarize_changes, switch_modes).

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• oraios.github.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add the rest of the Serena MCP tool names</issue_title>
<issue_description>In #357 we added two tools of the Serena MCP server, but there are of course more. Here is the rest of the info:

Problem

In VS Code, Serena’s MCP tools show up with VS Code-specific, fully-qualified command IDs like:

• mcp_oraios_serena_activate_project → “Serena: Activate Project”
• mcp_oraios_serena_get_current_config → “Serena: Get Current Config”

However, only a couple of these IDs are easy to discover via “References” in the VS Code workspace, and it’s unclear what the complete list of Serena MCP tool command IDs is in the VS Code format.

This makes it harder to:

• document usage,
• build keybindings / command palettes / automation around these commands,
• quickly verify which tools are available in a given context.

Proposal

Please add a generated/maintained list of Serena MCP tools in the exact VS Code command-id format:

mcp_oraios_serena_<tool_name>

…where <tool_name> is Serena’s MCP tool name (e.g. activate_project, get_current_config, etc.).

Requested output format

A single list (in docs and/or in-repo) like:

• mcp_oraios_serena_activate_project → Serena: Activate Project
• mcp_oraios_serena_get_current_config → Serena: Get Current Config
• mcp_oraios_serena_<...> → Serena: <...>

Notes:

• The left side should be exactly the command ID VS Code uses.
• The right side should match the human-readable title shown by VS Code (“Serena: …”).

Expected tool coverage

At minimum, include all tools exposed by Serena’s MCP server (i.e., the same set that would appear in an MCP client’s tool list), such as those documented in the “List of Tools” page (e.g. find_symbol, search_for_pattern, replace_symbol_body, etc.), plus any optional/context-dependent tools.

If some tools are context-dependent (e.g. disabled in ide single-project contexts), please still list them but annotate them (e.g. “optional”, “requires active project”, “JetBrains backend only”, etc.).

Suggested implementation (optional)

One of:

1. Add a small script that introspects the ToolRegistry / MCP server tool list and emits a Markdown file mapping:
   • mcp_oraios_serena_<name> → “Serena: <Title>”
2. Or add an explicit doc section stating how VS Code formats the IDs and provide the canonical list.

Acceptance criteria

• Repo contains a canonical mapping for all Serena MCP tools:
  • mcp_oraios_serena_<tool> → “Serena: <Title>”
• Easy for users to copy/paste for keybindings or automation.
• Updated automatically or clearly documented as generated.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Add the rest of the Serena MCP tool names #360

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.