feat: add remaining toolbox server flag

[Yuan325]

Add remaining CLI flags for the server published on official mcp registry.

ref: https://googleapis.github.io/genai-toolbox/reference/cli/

note: mcp registry do not support shorthand flag (there are no options to defined an alternate name). The only way is to define them as separate named arguments but it may not work well since both would try to set the same underlying value.

[gemini-code-assist]

Summary of Changes

Hello @Yuan325, I'm Gemini Code Assist¹! 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 significantly expands the command-line interface for the genai-toolbox server by incorporating a comprehensive set of new flags. These additions enhance the server's configurability, offering greater control over tool loading, logging formats, telemetry integration, and overall operational behavior, aligning with the official MCP registry specifications.

Highlights

• Tool Configuration Flags: Added new CLI flags, --tools-files and --tools-folder, to allow for more flexible specification of tool configurations from multiple files or an entire directory.
• Logging and Server Behavior Control: Introduced --logging-format for choosing between standard and JSON logging, and --disable-reload to control dynamic reloading of tool files. Flags like --stdio for MCP STDIO listening and --ui for launching the web server were also added.
• Telemetry Integration: Implemented several telemetry-related flags, including --telemetry-gcp for Google Cloud Monitoring, --telemetry-otlp for OpenTelemetry Protocol, and --telemetry-service-name to customize service identification.
• General Utility Flags: Standard command-line utility flags --help and --version have been added for better user experience and information retrieval.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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

[gemini-code-assist]

Code Review

This pull request adds the remaining CLI flags for the server to the server.json manifest, which is used by the MCP registry. The changes look good overall. My feedback focuses on improving the descriptions of the newly added flags for better clarity, usability, and to highlight a security consideration.