Skip to content

fix: namespace tool names for multiple MCP instances - #100

Open
Oscar-Williams wants to merge 1 commit into
designcomputer:mainfrom
Oscar-Williams:oscar/tool-name-prefix
Open

Oscar-Williams wants to merge 1 commit into
designcomputer:mainfrom
Oscar-Williams:oscar/tool-name-prefix

Conversation

@Oscar-Williams

Copy link
Copy Markdown

Summary

Allow multiple MySQL MCP Server instances to coexist in one client by applying an optional TOOL_NAME_PREFIX to tool discovery, dispatch, descriptions, and workflow prompts. The default empty prefix keeps existing tool names unchanged.

Verification

  • python -m pytest -q — 29 passed, 1 skipped
  • python -m compileall -q src tests
  • ruff check --select E9,F63,F7,F82 src tests
  • git diff --check

Fixes #99

The author defined the scope and reviewed the final diff; Codex assisted with implementation and automated tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Tool name conflicts when running multiple MCP server instances with different databases

1 participant