Update gemspec to reflect mcp naming
#24
Conversation
|
I think that In case publishing is not possible for some reason, contacting RubyGems would be advisable: From a long-term perspective, a more descriptive name may be preferable to an abbreviation. A unique name, rather than an abbreviated one that might cause conflicts, is likely to be clearer for users. |
we've worked with RubyGems to claim https://rubygems.org/gems/mcp - MCP is established as an acronym in the sdks for other languages, so |
|
I see. I might have been too influenced by an LSP SDK gem: Indeed, aligning with SDKs in other languages could be an option. Thank you for the explanation! |
|
|
topherbullock
force-pushed
the
update-gemspec
branch
from
1764325 to
bf07d4a
Compare
Follow-up to modelcontextprotocol#24. This PR fixes the following error when using `bin/console`: ```console $ bin/console /Users/koic/.rbenv/versions/3.4.4/lib/ruby/3.4.0/bundled_gems.rb:82: in 'Kernel.require': cannot load such file -- model_context_protocol (LoadError) from /Users/koic/.rbenv/versions/3.4.4/lib/ruby/3.4.0/bundled_gems.rb:82: in 'block (2 levels) in Kernel#replace_require' from bin/console:5:in '<main>' ```
Follow-up to modelcontextprotocol#24. The directory structure of the product code and test code is expected to match.
Follow-up to modelcontextprotocol#24. lib/mcp-ruby.rb was removed in modelcontextprotocol#24.
Motivation and Context
the gem will be published to RubyGems under https://rubygems.org/gems/mcp as
mcp, so gemspec, lib structure and naming should reflect this.How Has This Been Tested?
moved files, renamed constants, ran tests; CI is green
Breaking Changes
none.
ModelContextProtocolis aliased toMCPto allow backward compatibility if the gem has been leveraged using git instead of RubyGems by intrepid users.Types of changes
Checklist
Additional context
n/a