Claude agent: preserve configured MCP server names in SDK tool names (no index-based renaming)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4.6k
- Forks
- 251
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 34
Description
Request
Guarantee that MCP server names configured via ACP mcpServers are preserved verbatim in the SDK tool names for the packaged Claude agent (mcp__<configured-name>__<tool>). If the current adapter renames servers to index-based names (mcp-1, mcp-2, …), please fix it, and add a regression test on the tool-name shape.
Why
Observed with the 0.1.x adapter (@rivet-dev/agent-os-claude), where servers were renamed by index:
- Tool names became
mcp__mcp-1__ask_questioninstead ofmcp__deepwiki__ask_question, which hurts the model's tool selection and makes tool-call logs/permission prompts unreadable. - Tool identity is unstable: adding/removing a server shifts the indices, so allowlists or analytics keyed by tool name silently break.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the packaged Claude agent adapter that handles ACP mcpServers and inspect how server names become SDK tool names. Add the requested regression test for the tool-name shape; this is done when configured names such as deepwiki remain verbatim instead of becoming index-based names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100