[liang0417]

Summary

• clarify that registered capability names follow each server's existing public convention
• document snake_case for filesystem and memory, and kebab-case for everything
• warn against renaming published tools, prompts, or resources only to change casing

Closes #4892

Verification

• confirmed all 14 filesystem and 9 memory tool registrations use snake_case
• confirmed everything tool registrations use kebab-case
• git diff --check passes

Testing

Documentation-only change; no runtime code changed.

[cliffhall]

Thank you for this pull request, and apologies for the long wait for a response.

Since it was opened, the reference servers have been rebuilt for the 2026-07-28 MCP specification (#4857) and released as v2 (2.0.0 on npm for the TypeScript servers, 2026.10.19 on PyPI for the Python servers). The code this PR changes has been replaced, and the behavior it addresses has either been fixed in v2 or no longer exists in the same form.

This is not a judgment on the change or on you; it's a consequence of the code it targets having been replaced. If the problem still happens on v2, please open a fresh issue with the version you're running and steps to reproduce. Note that this repository now accepts contributions as issues rather than pull requests from anyone but its maintainers; see CONTRIBUTING.md.

This is part of the backlog triage in #4875.