Context
Post-publish review (mcp-builder skill) flagged two deviations from MCP naming conventions. Both are preserved for backward compatibility with v0.1.0 installed users. This issue documents the deviations for future reference.
Deviations
1. Server name: `jd-intel-mcp` vs convention `{service}-mcp-server`
Skill recommends `github-mcp-server`, `slack-mcp-server`, etc. Ours is `jd-intel-mcp`.
Why not fix: Renaming orphans every user who has `"args": ["-y", "jd-intel-mcp"]` in their Claude Desktop config. Breaks for zero functional benefit.
2. Tool names: `fetch_jobs` vs convention `{service}{action}{resource}`
Skill recommends service prefixes like `github_create_issue` to avoid collision when users have many MCP servers installed. Ours are `fetch_jobs`, `search_registry`, `detect_ats` — no `jd_intel_` prefix.
Why not fix: Same backward-compat concern. Also: MCP client namespacing (tool appears as `mcp__jd-intel__fetch_jobs` in most clients) reduces collision risk in practice.
If collision ever becomes a real problem
Reserve for a hypothetical v1.0.0 major release with explicit breaking-change announcement and migration path. Not a concern at current scale.
References
Context
Post-publish review (mcp-builder skill) flagged two deviations from MCP naming conventions. Both are preserved for backward compatibility with v0.1.0 installed users. This issue documents the deviations for future reference.
Deviations
1. Server name: `jd-intel-mcp` vs convention `{service}-mcp-server`
Skill recommends `github-mcp-server`, `slack-mcp-server`, etc. Ours is `jd-intel-mcp`.
Why not fix: Renaming orphans every user who has `"args": ["-y", "jd-intel-mcp"]` in their Claude Desktop config. Breaks for zero functional benefit.
2. Tool names: `fetch_jobs` vs convention `{service}{action}{resource}`
Skill recommends service prefixes like `github_create_issue` to avoid collision when users have many MCP servers installed. Ours are `fetch_jobs`, `search_registry`, `detect_ats` — no `jd_intel_` prefix.
Why not fix: Same backward-compat concern. Also: MCP client namespacing (tool appears as `mcp__jd-intel__fetch_jobs` in most clients) reduces collision risk in practice.
If collision ever becomes a real problem
Reserve for a hypothetical v1.0.0 major release with explicit breaking-change announcement and migration path. Not a concern at current scale.
References