Skip to content

chore: remove @praha/byethrow MCP server, use documentation URL - #513

Merged
ryoppippi merged 1 commit into
mainfrom
remove-byethrow-mcp
Aug 15, 2025
Merged

chore: remove @praha/byethrow MCP server, use documentation URL#513
ryoppippi merged 1 commit into
mainfrom
remove-byethrow-mcp

Conversation

@ryoppippi

@ryoppippi ryoppippi commented Aug 15, 2025

Copy link
Copy Markdown
Member

Summary

  • Remove @praha/byethrow MCP server configuration from .mcp.json
  • Update CLAUDE.md to reference https://praha-inc.github.io/byethrow/llms.txt for byethrow documentation
  • Keep @praha/byethrow package dependency for Result type usage in the codebase

This change switches from using the MCP server for byethrow documentation to referencing the LLMs.txt URL directly in the documentation.

Test plan

  • Removed MCP server configuration from .mcp.json
  • Updated documentation reference in CLAUDE.md
  • Preserved package dependency for Result type usage
  • Verify byethrow Result type still works in codebase
  • Test that documentation URL is accessible

Summary by CodeRabbit

  • Documentation

    • Added a direct link to Byethrow error-handling documentation to aid troubleshooting.
  • Chores

    • Removed the deprecated Byethrow MCP server integration from the configuration, reducing the number of configured MCP servers by one. Remaining MCP server entries are unchanged.

@coderabbitai

coderabbitai Bot commented Aug 15, 2025

Copy link
Copy Markdown

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Caution

Review failed

The pull request is closed.

Walkthrough

Removed the "@praha/byethrow" MCP server entry from .mcp.json; other MCP entries remain unchanged. Added a documentation link under Error Handling in CLAUDE.md. No code or API changes.

Changes

Cohort / File(s) Summary
MCP Config Update
./.mcp.json
Deleted the mcpServers entry for "@praha/byethrow" (stdio via bun x @praha/byethrow-mcp). Other server configs unchanged.
Docs Update
./CLAUDE.md
Added a documentation bullet linking to https://praha-inc.github.io/byethrow/llms.txt under Error Handling.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Poem

A rabbit tidies config with care,
Snips a server no longer there.
Drops a link—hop, skip, through docs we go,
Fewer burrows, cleaner flow.
Thump-thump: the garden’s light—
One less tunnel, still runs right. 🥕

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.


📜 Recent review details

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.

📥 Commits

Reviewing files that changed from the base of the PR and between 9e2057f694b69eaf3391d8317d832bc019a1a8db and 2af7741.

📒 Files selected for processing (2)
  • .mcp.json (0 hunks)
  • CLAUDE.md (1 hunks)
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch remove-byethrow-mcp

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
🪧 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.

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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Summary of Changes

Hello @ryoppippi, 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 streamlines the project's configuration and documentation by removing the local MCP server setup for @praha/byethrow and instead pointing directly to its online documentation. It also removes the @praha/byethrow package from the project's dependencies, indicating a shift in how its Result type is utilized or managed within the codebase.

Highlights

  • MCP Server Configuration Removal: The configuration for the "@praha/byethrow" MCP server has been completely removed from the .mcp.json file.
  • Documentation Update: The CLAUDE.md documentation now directly references the official byethrow documentation URL (https://praha-inc.github.io/byethrow/llms.txt) for information regarding its Result type.
  • Package Dependency Change: The @praha/byethrow package has been removed from the package.json dependencies. This contradicts the PR description's claim to keep the dependency for Result type usage, suggesting the Result type might now be used without a direct dependency, or the dependency was only needed for the MCP server.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
❌ Deployment failed
View logs
ccusage-guide 9e2057f6 Aug 15 2025, 10:52 AM

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Aug 15, 2025

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
ccusage-guide 2af7741 Commit Preview URL

Branch Preview URL
Aug 15 2025, 10:56 AM

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

Copy link
Copy Markdown
Contributor

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 remove the @praha/byethrow MCP server configuration and update its documentation URL. While the changes in .mcp.json and CLAUDE.md are correct, there is a critical issue in package.json. The @praha/byethrow dependency is removed, which contradicts the pull request description stating it should be kept for Result type usage. This removal will break the build, as the package is imported in src/data-loader.ts. Please revert this change in package.json.

Comment thread package.json Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

critical

This line should not have been removed. The @praha/byethrow dependency is required for the Result type used in src/data-loader.ts, as confirmed by the PR description. Removing it will cause the build to fail. Please restore this dependency.

- Remove byethrow MCP server from .mcp.json

- Update CLAUDE.md to reference byethrow llms.txt documentation URL

- Keep @praha/byethrow package dependency for Result type usage
@ryoppippi
ryoppippi force-pushed the remove-byethrow-mcp branch from 9e2057f to 2af7741 Compare August 15, 2025 10:55
@ryoppippi ryoppippi changed the title Remove @praha/byethrow MCP server, use documentation URL chore: remove @praha/byethrow MCP server, use documentation URL Aug 15, 2025
@pkg-pr-new

pkg-pr-new Bot commented Aug 15, 2025

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/ryoppippi/ccusage@513

commit: 2af7741

@ryoppippi
ryoppippi merged commit ba87e3c into main Aug 15, 2025
12 of 14 checks passed
@ryoppippi
ryoppippi deleted the remove-byethrow-mcp branch August 15, 2025 10:55
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