Skip to content

fix: correct npm badge to point to @iqai/mcp-near-intent-swaps package#30

Merged
Royal-lobster merged 1 commit intomainfrom
fix/npm-badge
Jan 27, 2026
Merged

fix: correct npm badge to point to @iqai/mcp-near-intent-swaps package#30
Royal-lobster merged 1 commit intomainfrom
fix/npm-badge

Conversation

@Royal-lobster
Copy link
Copy Markdown
Member

Summary

  • Changed package name from @iqai/mcp-near-intents to @iqai/mcp-near-intent-swaps
  • Updated bin name to match package name
  • Fixed npm badge URL in README to point to correct package
  • Updated all npx commands, git clone URLs, and configuration examples

Test plan

  • Verified package.json name is correct
  • Verified npm badge URL points to correct package
  • Verified all README references use correct package name

🤖 Generated with Claude Code

- Changed package name from @iqai/mcp-near-intents to @iqai/mcp-near-intent-swaps
- Updated bin name to match package name
- Fixed npm badge URL in README to point to correct package
- Updated all npx commands, git clone URLs, and configuration examples

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @Royal-lobster, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical naming inconsistency by updating the package name for the NEAR Intent Swaps MCP Server. The changes ensure that all documentation, installation instructions, and internal configurations correctly reference the @iqai/mcp-near-intent-swaps package, preventing potential issues for users attempting to install, build, or integrate the server. This provides a consistent and accurate experience for developers.

Highlights

  • Package Name Correction: The primary package name has been corrected from @iqai/mcp-near-intents to @iqai/mcp-near-intent-swaps across all relevant files.
  • Documentation Updates: The README.md file has been updated to reflect the new package name in the npm badge URL, npx command examples, git clone instructions, and configuration snippets.
  • Project Metadata Alignment: The package.json file now correctly lists the new package name, an updated description, and the corresponding binary name.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@Royal-lobster Royal-lobster merged commit ffa2752 into main Jan 27, 2026
1 check passed
@Royal-lobster Royal-lobster deleted the fix/npm-badge branch January 27, 2026 23:15
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request aims to rename the package to @iqai/mcp-near-intent-swaps. The changes in package.json and README.md are correct and consistent with this goal. I've added one comment regarding the scope of the renaming, as some internal references to the old name seem to have been missed. Once that is addressed, this PR will be in great shape.

Comment on lines +2 to 9
"name": "@iqai/mcp-near-intent-swaps",
"version": "0.0.11",
"description": "An MCP server for NEAR intents swap using the Defuse Protocol one-click SDK.",
"description": "An MCP server for NEAR intent swaps using the Defuse Protocol one-click SDK.",
"main": "dist/index.js",
"type": "module",
"bin": {
"mcp-near-intents": "dist/index.js"
"mcp-near-intent-swaps": "dist/index.js"
},
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

While the package name, description, and binary name are correctly updated here, the renaming seems incomplete across the project. There are still several references to the old name that should be updated for consistency.

For example:

  • src/index.ts still contains multiple references to "NEAR Intents MCP Server" in log messages and in the FastMCP constructor.
  • The tool description for GET_NEAR_SWAP_TOKENS in src/tools/near-swap-tokens.ts still refers to "NEAR Intents".

Please update all remaining occurrences of the old name to ensure the renaming is applied consistently throughout the codebase.

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.

1 participant