mistake

[maxcoto]

Summary by CodeRabbit

• New Features

  • Added comprehensive static and dynamic Ethereum blockchain tools, including querying balances, transactions, contract interactions, ENS resolution, and NFT utilities.
  • Integrated dynamic tool registration for contract-specific and protocol-based operations.
  • Introduced Supabase client integration for enhanced data access.

• Chores

  • Updated package dependencies to include Supabase and ethers.js.
  • Improved environment variable management by ignoring .env files in version control.

• Refactor

  • Reorganized tool registration into static and dynamic modules for better maintainability and scalability.

• Revert

  • Removed legacy tool registration and configuration files to streamline the codebase.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes introduce a modularized approach to EVM tool registration by splitting static and dynamic tool registration into separate modules. New mappings for chain API keys and endpoints are added. Supabase client integration is established. The .env file is now ignored, and some configuration and legacy files are removed or replaced.

Changes

File(s)	Change Summary
.cursor/mcp.json, src/core/tools.ts	Deleted MCP server config and legacy EVM tool registration module.
.gitignore	Added .env to ignored files.
package.json	Added dependencies: @supabase/ssr, @supabase/supabase-js, and ethers.
src/core/chains.ts	Added scanApiKeyMap and endpointMap constants for chain API keys and explorer endpoints.
src/core/common_tools.ts, src/core/static_tools.ts	Introduced new modules for static EVM tool registration on MCP server.
src/core/dynamic_tools.ts	New module for dynamic EVM tool registration, supporting protocol and contract-based tools.
src/lib/supabase/server.ts	Added Supabase client creation utility using environment variables.
src/server/server.ts	Updated server setup to register static and dynamic tools separately, with dynamic registration now asynchronous.

Sequence Diagram(s)

sequenceDiagram
    participant Admin as Server Startup
    participant MCP as MCP Server
    participant Static as Static Tools Module
    participant Dynamic as Dynamic Tools Module

    Admin->>Static: registerStaticTools(MCP)
    Admin->>Dynamic: await registerDynamicTools(MCP)
    Static-->>MCP: Registers static EVM tools
    Dynamic-->>MCP: Registers dynamic EVM tools (protocol/contract-based)

Loading

Poem

A hop, a skip, a modular leap,
Static and dynamic tools we now keep.
With Supabase joined and chains mapped anew,
The server starts fresh, with a clearer view.
Old files retire, new features ignite—
Rabbits code onward, through day and night!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cf63e94 and 55044cd.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (10)

• .cursor/mcp.json (0 hunks)
• .gitignore (1 hunks)
• package.json (1 hunks)
• src/core/chains.ts (1 hunks)
• src/core/common_tools.ts (1 hunks)
• src/core/dynamic_tools.ts (1 hunks)
• src/core/static_tools.ts (1 hunks)
• src/core/tools.ts (0 hunks)
• src/lib/supabase/server.ts (1 hunks)
• src/server/server.ts (2 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.