Skip to content

Separate procedures for running a self-hosted MCP server to a new page#671

Merged
kmoscoe merged 186 commits intodatacommonsorg:masterfrom
kmoscoe:split
Feb 5, 2026
Merged

Separate procedures for running a self-hosted MCP server to a new page#671
kmoscoe merged 186 commits intodatacommonsorg:masterfrom
kmoscoe:split

Conversation

@kmoscoe
Copy link
Copy Markdown
Contributor

@kmoscoe kmoscoe commented Feb 4, 2026

This PR refactors the "advanced" instructions for self hosting into a separate page, updates various links, and incorporates some additional suggestions from Christie on PR #669.

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

kmoscoe and others added 30 commits June 11, 2025 19:07
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @kmoscoe, 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 significantly improves the organization and clarity of the Data Commons MCP server documentation. By extracting the detailed procedures for running a self-hosted MCP server into its own page, the PR ensures that users can more easily find instructions relevant to their specific deployment needs, whether they are using a Custom Data Commons instance or setting up a general self-hosted server. This restructuring, along with updated links and minor content refinements, streamlines the user experience and provides a more focused guide for different MCP server configurations.

Highlights

  • Documentation Refactoring: The advanced instructions for running a self-hosted Data Commons MCP server have been moved from mcp/run_tools.md to a new, dedicated page: mcp/host_server.md.
  • Link Updates and Clarity: Various internal links across the documentation have been updated to reflect the new page structure and improve navigation, ensuring users are directed to the correct guide for their specific MCP server setup.
  • Content Refinements: Existing documentation pages have been updated to clarify their scope, focusing on either centrally hosted MCP server usage or Custom Data Commons instances, and incorporating additional suggestions from a previous pull request (Overhaul MCP docs for new hosted server #669).
Changelog
  • custom_dc/run_mcp_tools.md
    • Renamed the page title from "Run an MCP server" to "Run MCP tools".
    • Updated the introductory text to include a link to the Data Commons MCP server PyPI project.
    • Modified internal links to reference the newly created mcp/host_server.md for general self-hosting instructions.
    • Removed trailing blank lines.
  • mcp/host_server.md
    • Added a new documentation page dedicated to running a self-hosted Data Commons MCP server.
    • This page details procedures for both local server/local agent (Stdio) and remote server/local agent (HTTP) configurations.
    • Includes prerequisites such as the Data Commons API key and uv installation, along with configuration examples for Gemini CLI and sample agents.
  • mcp/index.md
    • Updated the "Clients" section to provide clearer guidance on where to find instructions for using the hosted server versus self-hosted deployments, linking to the new host_server.md page.
  • mcp/run_tools.md
    • Revised the introductory section to explicitly state that this page covers connecting to the centrally hosted server and directs users to host_server.md for advanced self-hosting scenarios.
    • Removed the extensive "Advanced: Run your own MCP server" section, as its content has been migrated to mcp/host_server.md.
    • Deleted a redundant tip about a Colab notebook, which is now present in the new self-hosting guide.
    • Adjusted a note regarding Gemini CLI configuration for improved wording.
Activity
  • No specific activity (comments, reviews, or progress updates) was provided in the context.
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.

Copy link
Copy Markdown
Contributor

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

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 successfully refactors the documentation by moving the instructions for self-hosting an MCP server to a new, dedicated page. This improves the structure and readability of the documentation. The links and titles have been updated accordingly across multiple files. I've found a few issues in the new mcp/host_server.md file, including incorrect comment syntax in a Python code block, an invalid JSON example, and a protocol mismatch in a URL. My review includes suggestions to fix these issues.

Comment thread mcp/host_server.md
Comment thread mcp/host_server.md Outdated
Comment thread mcp/host_server.md Outdated
@kmoscoe kmoscoe changed the title Separate procedures for running a self-hosted MCP server to a separate page Separate procedures for running a self-hosted MCP server to a new page Feb 4, 2026
kmoscoe and others added 4 commits February 4, 2026 13:28
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@kmoscoe kmoscoe requested review from beets and clincoln8 February 4, 2026 21:30
Copy link
Copy Markdown
Contributor

@beets beets left a comment

Choose a reason for hiding this comment

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

thanks kara!

@kmoscoe kmoscoe merged commit dfcc37b into datacommonsorg:master Feb 5, 2026
2 checks passed
@kmoscoe kmoscoe deleted the split branch February 5, 2026 19:21
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.

2 participants