Overhaul MCP docs for new hosted server

[kmoscoe]

This PR restructures the docs as follows:

• Modifies the graphic and adds another one for the new deployment
• Moves all custom instance-specific content into a new page under the custom DC docs
• Removes "develop an agent" page
• Removes procedures for creating a custom Gemini CLI extension

Staged at https://bullie.svl.corp.google.com:4000

[gemini-code-assist]

Summary of Changes

Hello @kmoscoe, 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 undertakes a comprehensive overhaul of the Model Context Protocol (MCP) documentation. The primary objective is to align the documentation with the introduction of a new hosted MCP server, providing clearer guidance for users. This involves a significant reorganization of content, updating visual aids, centralizing information pertinent to custom Data Commons instances, and removing obsolete sections to enhance clarity and user experience.

Highlights

• Documentation Restructuring: The Model Context Protocol (MCP) documentation has been significantly reorganized to better reflect the new hosted server architecture.
• Graphic Updates: New and modified graphics have been introduced to visually represent the updated deployment models.
• Custom Instance Content Consolidation: All content specific to custom Data Commons instances has been moved into a dedicated new page under the custom DC documentation.
• Removal of Outdated Pages: The 'develop an agent' page and procedures for creating custom Gemini CLI extensions have been removed, streamlining the documentation.

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 overhauls the MCP documentation to reflect the availability of a new hosted server. It restructures the content by moving custom instance-specific information to a new page and removing outdated pages about agent development. The changes make the documentation clearer and more focused on the new recommended setup.

My review focuses on ensuring the correctness of the updated instructions, fixing broken links, and improving clarity and consistency across the documentation. I've found a few issues, including incorrect URLs, broken internal links, and potentially misleading instructions that could block users. I've provided suggestions to address these. Overall, this is a great improvement to the documentation.