fix: correct JSON key for client capabilities

[TBXark]

The current client has a BUG. Specifically, running examples/filesystem_stdio_client will report an error. Because one of the JSON keys is set incorrectly.

2025/04/23 13:56:15 Failed to initialize: [
  {
    "code": "invalid_type",
    "expected": "object",
    "received": "undefined",
    "path": [
      "params",
      "capabilities"
    ],
    "message": "Required"
  }
]

Summary by CodeRabbit

• Bug Fixes
  • Corrected the JSON key used for capabilities in client initialization requests to ensure proper communication with the server.

[coderabbitai]

Walkthrough

The change updates the JSON field tag for the Capabilities field within the params struct in the Initialize method of the client code. Specifically, the tag was changed from "serverCapabilities" to "capabilities", altering the key used in the JSON payload during client initialization. No other modifications to logic or exported entities were made.

Changes

File(s)	Change Summary
client/client.go	Updated the JSON field tag for Capabilities in the Initialize method's params struct from "serverCapabilities" to "capabilities".

---

📜 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 781b732 and 6f258c8.

📒 Files selected for processing (1)

• client/client.go (1 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (1)

client/client.go (1)

mcp/types.go (1)

• ClientCapabilities (323-333)

🔇 Additional comments (1)

client/client.go (1)

134-134: Correct fix for the JSON key field.

This change properly addresses the issue described in the PR where the client failed to initialize because of an incorrect JSON key. By changing the field tag from "serverCapabilities" to "capabilities", the client will now properly send the capabilities object with the expected key name that matches the protocol specification.

This aligns with the ClientCapabilities struct defined in mcp/types.go and fixes the type validation error that occurred when running the example client.

✨ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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.

[dugenkui03]

lgtm

[TBXark]

lgtm

I found that this was changed in your latest commit. I don't quite understand the reason for this change. If I change it back, will there be other problems? But currently the srdio example does fail to initialize.