docs: improve ETHID MCP quick setup instructions

[schmidsi]

• Clarify that setup methods are options to choose from
• Add Claude Code setup as the first option with simple command
• Rename existing options for consistency

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Reorganized Quick Setup into three clear options: Claude Code Setup, Use the online server, and Run it locally.
  • Added a concrete CLI command for Claude Code to configure the MCP transport to the SSE endpoint.
  • Clarified online server access with explicit SSE and HTTP endpoints shown in a dedicated code block.
  • Simplified local setup to a single install command, removing the previous additional step.
  • Overall, provides clearer, option-based guidance and streamlined setup paths.

[vercel]

@schmidsi is attempting to deploy a commit to the EFP Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

Reorganized ETHID MCP Quick Setup into three options (Claude Code, Online Server, Local). Added explicit endpoints for SSE and HTTP. Updated commands, including a Claude CLI example and simplified local install to only npm install.

Changes

Cohort / File(s)	Summary
Docs: ETHID MCP Quick Setup pages/docs/ai-tools/ethid-mcp.mdx	Replaced linear setup with three options; added Claude Code CLI config; documented SSE/HTTP endpoints; simplified local setup to npm install only; adjusted headings and code blocks accordingly.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related issues

• Add comprehensive documentation for ethid-mcp server under new "AI Tools" category #19 — Aligns with reorganizing ETHID‑MCP docs under AI Tools and clarifying endpoints and setup options.

Poem

A rabbit taps keys with a gentle hop,
Three paths to ETHID—pick your stop.
SSE breezes, HTTP flows,
Claude whispers configs it knows.
Local burrow, npm install—
Docs now tidy, carrots for all! 🥕

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

pages/docs/ai-tools/ethid-mcp.mdx (3)

9-16: Standardize MCP server name to match the rest of the docs

Elsewhere (config JSON, Claude Desktop config, troubleshooting) the server is named “ethid-mcp”. Using “ethid” here will confuse users and break copy-paste consistency.

Apply this diff to align the name:

-```bash
-claude mcp add --transport sse ethid https://ethid-mcp.efp.workers.dev/sse
-```
+```bash
+claude mcp add --transport sse ethid-mcp https://ethid-mcp.efp.workers.dev/sse
+```

Optional: consider titling the section “Claude Desktop/CLI Setup” to be explicit that this uses the Claude CLI.

---

17-27: Verify client list and tighten language for MCP compatibility

“Wireshark” is a network analyzer, not an MCP client. “ChatGPT” also doesn’t natively support MCP. Safer wording avoids misleading examples.

Apply this diff to adjust the client list and code block language (URLs aren’t bash commands):

-Use one of the following endpoints to connect the MCP server to your AI assistant (Claude, Wireshark, ChatGPT, etc.).
+Use one of the following endpoints to connect the MCP server to your MCP-compatible client (e.g., Claude Desktop).

-```bash
+```text
 # Using the SSE endpoint
 https://ethid-mcp.efp.workers.dev/sse
 
 # Or HTTP endpoint
 https://ethid-mcp.efp.workers.dev

If you want, I can add a short, verified list of known MCP-compatible clients here.

---

`29-34`: **Confirm local steps; summary says “npm install” only, but doc still includes “npm run dev”**

The AI summary mentions simplifying local setup to only npm install, yet this section still includes npm run dev. If the intent is to keep both (recommended), nothing to change; if not, remove the second line to match the summary.




Two alternatives:

- Keep both (recommended for a runnable local setup): no change.
- Or, to match the summary, remove the dev step:

```diff
 ```bash
 npm install
-npm run dev

Optionally, consider adding a one-liner above with clone instructions for completeness (clone + cd) if users may land here directly.

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

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

**💡 Knowledge Base configuration:**

- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between a9d3bcbde7a95c617f10c228877853cc7b0c61df and e4380a84a51b78e72c4d93695532d4df0b1d5730.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `pages/docs/ai-tools/ethid-mcp.mdx` (2 hunks)

</details>

<details>
<summary>🔇 Additional comments (1)</summary><blockquote>

<details>
<summary>pages/docs/ai-tools/ethid-mcp.mdx (1)</summary>

`7-8`: **Good clarification that the methods are alternatives**

The “Choose one of the following options…” line makes the branching setup paths explicit.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->